Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a332f13cdc915e31e1431eb7f9b1f6f383ebd87992360275ae26e011a3bf3ac5

Tx prefix hash: f362e532f7c9e9496124f49c50d56ed7ca7cfea6d3d224137f4f5bc1870e766c
Tx public key: a9fdbdb23ca72df7232f1739e5f5be15bd2e0f4ad568544e3fe87507f7e7764f
Timestamp: 1741978391 Timestamp [UCT]: 2025-03-14 18:53:11 Age [y:d:h:m:s]: 00:061:01:27:50
Block: 1239313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43667 RingCT/type: yes/0
Extra: 01a9fdbdb23ca72df7232f1739e5f5be15bd2e0f4ad568544e3fe87507f7e7764f021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9d2e0fffc64d04ebf8b708c81c3e5070664eb4984147337efd1cce7f7926e4d 0.600000000000 1726278 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": 1239323, "vin": [ { "gen": { "height": 1239313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9d2e0fffc64d04ebf8b708c81c3e5070664eb4984147337efd1cce7f7926e4d" } } ], "extra": [ 1, 169, 253, 189, 178, 60, 167, 45, 247, 35, 47, 23, 57, 229, 245, 190, 21, 189, 46, 15, 74, 213, 104, 84, 78, 63, 232, 117, 7, 247, 231, 118, 79, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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