Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 405de301cee13ab6f22ac32188e8ff27466b201cec37ceff0698e70b8fde2dab

Tx prefix hash: ee2c09bf58c74d62c1bf93c0559fe85e230d3bcaf308f220fa2474909fc11e4c
Tx public key: 069496af6cdc64c0aacb3ddd23e8da7709b9f9d6bba5ed7bf54a9559c5bbaa6b
Timestamp: 1720894322 Timestamp [UCT]: 2024-07-13 18:12:02 Age [y:d:h:m:s]: 00:267:04:11:51
Block: 1064981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190857 RingCT/type: yes/0
Extra: 01069496af6cdc64c0aacb3ddd23e8da7709b9f9d6bba5ed7bf54a9559c5bbaa6b021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d55e7fe973a0a9a40111ec5424d5b9b633737cd2b341f60d45e7e1967b6e58e5 0.600000000000 1535522 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": 1064991, "vin": [ { "gen": { "height": 1064981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d55e7fe973a0a9a40111ec5424d5b9b633737cd2b341f60d45e7e1967b6e58e5" } } ], "extra": [ 1, 6, 148, 150, 175, 108, 220, 100, 192, 170, 203, 61, 221, 35, 232, 218, 119, 9, 185, 249, 214, 187, 165, 237, 123, 245, 74, 149, 89, 197, 187, 170, 107, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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