Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ba9fc13c011a033086f9296b6b8c311063e60d36d95a84a307506ceaed5020b

Tx prefix hash: 486830bb720e0e60f507773061fc7429abab0eaba0cf07b91ad4cdc97a361e8a
Tx public key: 6ef8a5c328c98d6c2315bc4a174ad22fa9fcab4c128f8d97fa6222ca31e2d5dc
Timestamp: 1757206157 Timestamp [UCT]: 2025-09-07 00:49:17 Age [y:d:h:m:s]: 00:060:01:00:46
Block: 1362994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42887 RingCT/type: yes/0
Extra: 016ef8a5c328c98d6c2315bc4a174ad22fa9fcab4c128f8d97fa6222ca31e2d5dc021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6dc9457eff31e09fb1234a9d30ca5c856b1fc99ea1bcbce56d4009f3803030e 0.600000000000 1851033 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": 1363004, "vin": [ { "gen": { "height": 1362994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6dc9457eff31e09fb1234a9d30ca5c856b1fc99ea1bcbce56d4009f3803030e" } } ], "extra": [ 1, 110, 248, 165, 195, 40, 201, 141, 108, 35, 21, 188, 74, 23, 74, 210, 47, 169, 252, 171, 76, 18, 143, 141, 151, 250, 98, 34, 202, 49, 226, 213, 220, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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