Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39a5c3ace594cca5a34c7c87c507f6e8fe38cc9dc240f5584d20085adad1029e

Tx prefix hash: 0516fc094ddb49a15bddb120fd060b20b692f557c5ae2d48cb82af9c59e7fb2e
Tx public key: 186db8eabbb3834db5318763e352fe42bc0778b7ecdce2d1b2eb30207f2f7b35
Timestamp: 1750436646 Timestamp [UCT]: 2025-06-20 16:24:06 Age [y:d:h:m:s]: 00:152:15:37:23
Block: 1309162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106945 RingCT/type: yes/0
Extra: 01186db8eabbb3834db5318763e352fe42bc0778b7ecdce2d1b2eb30207f2f7b3502110000000fbf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 404b8a6634c5746af2c8606c8d7d9067f0fc856a0150140ffbf3d46c622127b4 0.600000000000 1796777 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": 1309172, "vin": [ { "gen": { "height": 1309162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "404b8a6634c5746af2c8606c8d7d9067f0fc856a0150140ffbf3d46c622127b4" } } ], "extra": [ 1, 24, 109, 184, 234, 187, 179, 131, 77, 181, 49, 135, 99, 227, 82, 254, 66, 188, 7, 120, 183, 236, 220, 226, 209, 178, 235, 48, 32, 127, 47, 123, 53, 2, 17, 0, 0, 0, 15, 191, 81, 178, 162, 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