Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 296f454273e3e96297b2706a73e6beed2eef9d282ec529f99e1b740bfecdc137

Tx prefix hash: 5de68f901a6657695993c2acb1cbdf0d13340cb635421ab800f89b2c71c2adeb
Tx public key: d98b7eccbbfa87805d98fd15b252165e5367d5d50ede3296d641e8b2ca21e821
Timestamp: 1742766198 Timestamp [UCT]: 2025-03-23 21:43:18 Age [y:d:h:m:s]: 00:045:06:29:20
Block: 1245810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32384 RingCT/type: yes/0
Extra: 01d98b7eccbbfa87805d98fd15b252165e5367d5d50ede3296d641e8b2ca21e821021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d5e3ab8bad7c1e171e457456f000d7009b7915331e5b1af371132f7e00e21b4 0.600000000000 1732801 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": 1245820, "vin": [ { "gen": { "height": 1245810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d5e3ab8bad7c1e171e457456f000d7009b7915331e5b1af371132f7e00e21b4" } } ], "extra": [ 1, 217, 139, 126, 204, 187, 250, 135, 128, 93, 152, 253, 21, 178, 82, 22, 94, 83, 103, 213, 213, 14, 222, 50, 150, 214, 65, 232, 178, 202, 33, 232, 33, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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