Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 10e9aa55bde0e013ecda3813d4fd92ba5331b1b8c11dd38817bb363a90b6ade0

Tx prefix hash: 657a6cd29de6cdbc68bb4cdd7671455369ba7417267f1ae76c8b6b6e50c57b0c
Tx public key: 883c58e5b82c684cc004af6340676b502044a14d9f476e9b7c609dae3a5db285
Timestamp: 1724716530 Timestamp [UCT]: 2024-08-26 23:55:30 Age [y:d:h:m:s]: 01:071:18:13:10
Block: 1096649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309726 RingCT/type: yes/0
Extra: 01883c58e5b82c684cc004af6340676b502044a14d9f476e9b7c609dae3a5db285021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78dfb03b30c956912ae2d7b20ea7082373fec690c7f390da73c0da5a0f9bee9e 0.600000000000 1571842 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1096659, "vin": [ { "gen": { "height": 1096649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78dfb03b30c956912ae2d7b20ea7082373fec690c7f390da73c0da5a0f9bee9e" } } ], "extra": [ 1, 136, 60, 88, 229, 184, 44, 104, 76, 192, 4, 175, 99, 64, 103, 107, 80, 32, 68, 161, 77, 159, 71, 110, 155, 124, 96, 157, 174, 58, 93, 178, 133, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8