Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d12f20e9db09fe61e2eea2d6bb55398a1598c901ffeecce8fdf829ee2c1ec90e

Tx prefix hash: e0e0c929c40f6abc952839e265ce1fc61064bcf8bbbbff622e0856906029f96a
Tx public key: 58ca55501d704b91be4d2a05abeeadf2a48d56ed73b313f912968a61d6f22d01
Timestamp: 1709608960 Timestamp [UCT]: 2024-03-05 03:22:40 Age [y:d:h:m:s]: 01:107:13:49:45
Block: 971413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337777 RingCT/type: yes/0
Extra: 0158ca55501d704b91be4d2a05abeeadf2a48d56ed73b313f912968a61d6f22d010211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71c383545b8a95c180d57b301522a5175464a8e7141d9cc3b8aad71b6a7421bd 0.600000000000 1431308 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": 971423, "vin": [ { "gen": { "height": 971413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71c383545b8a95c180d57b301522a5175464a8e7141d9cc3b8aad71b6a7421bd" } } ], "extra": [ 1, 88, 202, 85, 80, 29, 112, 75, 145, 190, 77, 42, 5, 171, 238, 173, 242, 164, 141, 86, 237, 115, 179, 19, 249, 18, 150, 138, 97, 214, 242, 45, 1, 2, 17, 0, 0, 0, 4, 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