Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05454211a251f336960e976f283abf8062679d33476c7fc39a070c13ba6f8906

Tx prefix hash: 888a7bd3307c495299fd5b8808de1d0d96c5f2c2e84db7d17379319488c83b9e
Tx public key: fffb1d7c1e713f88a4e7a2fdb8be2ccead0854cfd76a87bbac23228849a45e3a
Timestamp: 1761115858 Timestamp [UCT]: 2025-10-22 06:50:58 Age [y:d:h:m:s]: 00:030:10:28:48
Block: 1395314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21776 RingCT/type: yes/0
Extra: 01fffb1d7c1e713f88a4e7a2fdb8be2ccead0854cfd76a87bbac23228849a45e3a021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90820a3894da4dee07a06608fe427acee0fe284be869ade4a05a9314bfe09d2f 0.600000000000 1883591 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": 1395324, "vin": [ { "gen": { "height": 1395314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90820a3894da4dee07a06608fe427acee0fe284be869ade4a05a9314bfe09d2f" } } ], "extra": [ 1, 255, 251, 29, 124, 30, 113, 63, 136, 164, 231, 162, 253, 184, 190, 44, 206, 173, 8, 84, 207, 215, 106, 135, 187, 172, 35, 34, 136, 73, 164, 94, 58, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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