Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc57696ad139626fd32704da39beff5b734f8c5b29d04d5806f1367e7cd17c6c

Tx prefix hash: b58628118c60c017a4dc28c9d456b76936255d8d37d44158105f9475180f7c0c
Tx public key: 4bc60b4fd21dd9068fb5aae4f25b27e3f137328f4a11136a4011ca22f74629cf
Timestamp: 1764140316 Timestamp [UCT]: 2025-11-26 06:58:36 Age [y:d:h:m:s]: 00:000:06:48:14
Block: 1420370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201 RingCT/type: yes/0
Extra: 014bc60b4fd21dd9068fb5aae4f25b27e3f137328f4a11136a4011ca22f74629cf021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70450e44ac0ed359517700478280773e62d33ddfd0904a5f61c4bac49c5e1966 0.600000000000 1908913 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": 1420380, "vin": [ { "gen": { "height": 1420370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70450e44ac0ed359517700478280773e62d33ddfd0904a5f61c4bac49c5e1966" } } ], "extra": [ 1, 75, 198, 11, 79, 210, 29, 217, 6, 143, 181, 170, 228, 242, 91, 39, 227, 241, 55, 50, 143, 74, 17, 19, 106, 64, 17, 202, 34, 247, 70, 41, 207, 2, 17, 0, 0, 0, 1, 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