Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 481d6318b852b932fb9ce3c34d5d99b26c7e07940ae993652c1a4cc308d4a434

Tx prefix hash: 3600b356268cc5bc242feb5bcf33b1daa8bba5889104f0271366cac0921c5888
Tx public key: 5cf370491719ea64b414302389a1be0e79327dc42674b4c67535ce5a072d5457
Timestamp: 1719886268 Timestamp [UCT]: 2024-07-02 02:11:08 Age [y:d:h:m:s]: 01:129:13:31:25
Block: 1056608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351133 RingCT/type: yes/0
Extra: 015cf370491719ea64b414302389a1be0e79327dc42674b4c67535ce5a072d54570211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f789df572bd599c234aab6a216869d3d06d07c8c88cc233aa1368bd633a071d 0.600000000000 1527023 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": 1056618, "vin": [ { "gen": { "height": 1056608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f789df572bd599c234aab6a216869d3d06d07c8c88cc233aa1368bd633a071d" } } ], "extra": [ 1, 92, 243, 112, 73, 23, 25, 234, 100, 180, 20, 48, 35, 137, 161, 190, 14, 121, 50, 125, 196, 38, 116, 180, 198, 117, 53, 206, 90, 7, 45, 84, 87, 2, 17, 0, 0, 0, 2, 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