Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5d8b2442dec8e31b42cc639c19dd72e3d3a5f71422787fd68de2ec4ced6474e

Tx prefix hash: 573fb3605f9e6f6d9707f61d7c99b42c3927f91ee2a7d6801f63ccfbf2ab708a
Tx public key: defed7a5ea9b2e3bec8de87579a039420af1c3601a4fbf01ecc992a823ae6999
Timestamp: 1766253159 Timestamp [UCT]: 2025-12-20 17:52:39 Age [y:d:h:m:s]: 00:000:23:35:27
Block: 1437885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 701 RingCT/type: yes/0
Extra: 01defed7a5ea9b2e3bec8de87579a039420af1c3601a4fbf01ecc992a823ae69990211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6340d818695f281a70f8247158683312153f238685b05f78f3d6efd5e48635b 0.600000000000 1926698 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": 1437895, "vin": [ { "gen": { "height": 1437885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6340d818695f281a70f8247158683312153f238685b05f78f3d6efd5e48635b" } } ], "extra": [ 1, 222, 254, 215, 165, 234, 155, 46, 59, 236, 141, 232, 117, 121, 160, 57, 66, 10, 241, 195, 96, 26, 79, 191, 1, 236, 201, 146, 168, 35, 174, 105, 153, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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