Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb19fa32edc3e1671ea3017b25a77319713a8abf4974abd626c883ba227f82f6

Tx prefix hash: 8a9fed75f18b60666885534aa761e00dc3443e1f2fb61540de9570e8f04a1f59
Tx public key: 02996ca705a13d434a86383f5d723b36b973ee8e5817372e318dfca9c3edc9d9
Timestamp: 1763688933 Timestamp [UCT]: 2025-11-21 01:35:33 Age [y:d:h:m:s]: 00:032:10:36:47
Block: 1416617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23233 RingCT/type: yes/0
Extra: 0102996ca705a13d434a86383f5d723b36b973ee8e5817372e318dfca9c3edc9d90211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f17c4b6c8f7408348960165cb78f2f83699c1d30c9d4c7023afde59ca254cbfc 0.600000000000 1905136 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": 1416627, "vin": [ { "gen": { "height": 1416617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f17c4b6c8f7408348960165cb78f2f83699c1d30c9d4c7023afde59ca254cbfc" } } ], "extra": [ 1, 2, 153, 108, 167, 5, 161, 61, 67, 74, 134, 56, 63, 93, 114, 59, 54, 185, 115, 238, 142, 88, 23, 55, 46, 49, 141, 252, 169, 195, 237, 201, 217, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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