Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96c1c027e0ced84ad2b258c3f92f854d267cb927de362a9df9632003bdf77de5

Tx prefix hash: 3344a7c7e10f10ac52ca4dc0df9516078e0aa75b0677490e4b3812ef3cb8b56c
Tx public key: 7e69492cb3d57ae1a381ccaa11140ca45032e8c2e7c4a0f85908dbf91c1f98b9
Timestamp: 1764039651 Timestamp [UCT]: 2025-11-25 03:00:51 Age [y:d:h:m:s]: 00:002:10:05:17
Block: 1419538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1736 RingCT/type: yes/0
Extra: 017e69492cb3d57ae1a381ccaa11140ca45032e8c2e7c4a0f85908dbf91c1f98b902110000000ad6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7cdd750152a901d2bc2ab44e23c3f205b932e953f4ef6231048f2e050c0d7d7 0.600000000000 1908075 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": 1419548, "vin": [ { "gen": { "height": 1419538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7cdd750152a901d2bc2ab44e23c3f205b932e953f4ef6231048f2e050c0d7d7" } } ], "extra": [ 1, 126, 105, 73, 44, 179, 213, 122, 225, 163, 129, 204, 170, 17, 20, 12, 164, 80, 50, 232, 194, 231, 196, 160, 248, 89, 8, 219, 249, 28, 31, 152, 185, 2, 17, 0, 0, 0, 10, 214, 225, 157, 124, 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