Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7717ad64fecdbbf547bc9beac7aa6f7a65538665ef6f6f2a39ed38a55d945737

Tx prefix hash: 1631b1892e1f8eba16c7ea317a712ee15eaa38fc18e2f2b08f13331f11b1c0dd
Tx public key: 4d6643eb686ac09c4b50b21e3277ee4bf63896d8c94d3a81d033cebb45cca3d7
Timestamp: 1745623660 Timestamp [UCT]: 2025-04-25 23:27:40 Age [y:d:h:m:s]: 00:155:19:39:50
Block: 1269451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109027 RingCT/type: yes/0
Extra: 014d6643eb686ac09c4b50b21e3277ee4bf63896d8c94d3a81d033cebb45cca3d70211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9b32d2332dbc5e23c3afdcafe83cefaebced62e07a6ed43e6e7b0931130a04d 0.600000000000 1756690 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": 1269461, "vin": [ { "gen": { "height": 1269451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9b32d2332dbc5e23c3afdcafe83cefaebced62e07a6ed43e6e7b0931130a04d" } } ], "extra": [ 1, 77, 102, 67, 235, 104, 106, 192, 156, 75, 80, 178, 30, 50, 119, 238, 75, 246, 56, 150, 216, 201, 77, 58, 129, 208, 51, 206, 187, 69, 204, 163, 215, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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