Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70b6c10e53f246b15942aacdb54e37073a89fb61899f1094a19feb4eb9b4eb71

Tx prefix hash: d2fb1cc59a32ee515314ff61e9cf51d58c63976541225abdb0895137aac501a1
Tx public key: 3b7e670618f57908aeb188273e838d2fb738e1ddd45c03a81236a5b1f9e80664
Timestamp: 1713553425 Timestamp [UCT]: 2024-04-19 19:03:45 Age [y:d:h:m:s]: 00:354:22:29:50
Block: 1004089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253759 RingCT/type: yes/0
Extra: 013b7e670618f57908aeb188273e838d2fb738e1ddd45c03a81236a5b1f9e806640211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 075b3c3dcb5ffe6d06a0452567704149a7071e58d2d4b818c60543e509119d1d 0.600000000000 1464655 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": 1004099, "vin": [ { "gen": { "height": 1004089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "075b3c3dcb5ffe6d06a0452567704149a7071e58d2d4b818c60543e509119d1d" } } ], "extra": [ 1, 59, 126, 103, 6, 24, 245, 121, 8, 174, 177, 136, 39, 62, 131, 141, 47, 183, 56, 225, 221, 212, 92, 3, 168, 18, 54, 165, 177, 249, 232, 6, 100, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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