Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72f3302834f376d49e80b290ae2b2a8696220d1e6a649b828e61e1567939fc22

Tx prefix hash: 5b51c14f418843656e65278ecddbe368f5d7f96912aa7aec6136286bb2cc412f
Tx public key: b188ff3255a683df65879b86e3077e4dae4619c7edfb22e414f62563b5b482fe
Timestamp: 1752625113 Timestamp [UCT]: 2025-07-16 00:18:33 Age [y:d:h:m:s]: 00:128:23:04:24
Block: 1326359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90915 RingCT/type: yes/0
Extra: 01b188ff3255a683df65879b86e3077e4dae4619c7edfb22e414f62563b5b482fe02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68d2eec93b21ad2cd8f291e5dd2dcdd8f8be4ec05ef0b7c5a81d266528b661c0 0.600000000000 1814110 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": 1326369, "vin": [ { "gen": { "height": 1326359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68d2eec93b21ad2cd8f291e5dd2dcdd8f8be4ec05ef0b7c5a81d266528b661c0" } } ], "extra": [ 1, 177, 136, 255, 50, 85, 166, 131, 223, 101, 135, 155, 134, 227, 7, 126, 77, 174, 70, 25, 199, 237, 251, 34, 228, 20, 246, 37, 99, 181, 180, 130, 254, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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