Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 657b562d088294b0f1fcf606153784187a12d5d35fbd2a21ba9c66b520885a7c

Tx prefix hash: 930f117418539ba1436d74b9258ced9d113eb6c74c26f8a473f916a73650986b
Tx public key: 37f7832b8792c32d77326b7edf3eb9bea35b8e5360120f569d5b0a772dafc46c
Timestamp: 1735908681 Timestamp [UCT]: 2025-01-03 12:51:21 Age [y:d:h:m:s]: 00:164:01:37:27
Block: 1189328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116972 RingCT/type: yes/0
Extra: 0137f7832b8792c32d77326b7edf3eb9bea35b8e5360120f569d5b0a772dafc46c021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cd56fe440fee9edd08e4d67459c1ac8aebd69a4b63d0e0a874955f3e66ca6ef 0.600000000000 1675837 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": 1189338, "vin": [ { "gen": { "height": 1189328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cd56fe440fee9edd08e4d67459c1ac8aebd69a4b63d0e0a874955f3e66ca6ef" } } ], "extra": [ 1, 55, 247, 131, 43, 135, 146, 195, 45, 119, 50, 107, 126, 223, 62, 185, 190, 163, 91, 142, 83, 96, 18, 15, 86, 157, 91, 10, 119, 45, 175, 196, 108, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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