Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d7c4d5394ab128cafb89ff937691dc778137585bfe05e5f27c20afd18b5453b

Tx prefix hash: 92535611614c6c711c947879710d1dec5d97659a6199b4419ebfc33c75ac8fb5
Tx public key: aba74b4bf93e7c4f4acc2dd35fd7f3e4b897772a7e8ac5a92a8654e3be2d6bf8
Timestamp: 1712082216 Timestamp [UCT]: 2024-04-02 18:23:36 Age [y:d:h:m:s]: 01:006:05:05:48
Block: 991880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265424 RingCT/type: yes/0
Extra: 01aba74b4bf93e7c4f4acc2dd35fd7f3e4b897772a7e8ac5a92a8654e3be2d6bf80211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 951596b3a7b7f0e536108b06a46b51c5c6eef1264fb1dc209a02402823422196 0.600000000000 1452216 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": 991890, "vin": [ { "gen": { "height": 991880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "951596b3a7b7f0e536108b06a46b51c5c6eef1264fb1dc209a02402823422196" } } ], "extra": [ 1, 171, 167, 75, 75, 249, 62, 124, 79, 74, 204, 45, 211, 95, 215, 243, 228, 184, 151, 119, 42, 126, 138, 197, 169, 42, 134, 84, 227, 190, 45, 107, 248, 2, 17, 0, 0, 0, 7, 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