Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 388a9730677a5b2e7f702627e9e4d528eff5245163e034bb4439efe2ebe2e4b5

Tx prefix hash: c5d4b0b8473e63e1036e38cf416d19f63e1c95ad9cc43e46d69b9d97ae1288f3
Tx public key: 4f1f92e8bfcfc0a2b09abcf2cbfc52765c94280a894a993a29b785b2d13e945d
Timestamp: 1717897104 Timestamp [UCT]: 2024-06-09 01:38:24 Age [y:d:h:m:s]: 00:228:11:31:29
Block: 1040122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163464 RingCT/type: yes/0
Extra: 014f1f92e8bfcfc0a2b09abcf2cbfc52765c94280a894a993a29b785b2d13e945d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3be390462e9fdb0f0c17c2bfc70bf27862c035d5bcf62ff3716eb20d25c01a04 0.600000000000 1508777 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": 1040132, "vin": [ { "gen": { "height": 1040122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3be390462e9fdb0f0c17c2bfc70bf27862c035d5bcf62ff3716eb20d25c01a04" } } ], "extra": [ 1, 79, 31, 146, 232, 191, 207, 192, 162, 176, 154, 188, 242, 203, 252, 82, 118, 92, 148, 40, 10, 137, 74, 153, 58, 41, 183, 133, 178, 209, 62, 148, 93, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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