Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7a6fd0f92c2ff217e875c15b17c59807ac7e44fdfe17706847aa09b05413300

Tx prefix hash: c7d176e1c3d6e472b2269d95a8304a442ec65c39eff0b5a2aecf5affd2dacade
Tx public key: 6e5ac557ae6c15ac24c0296b9eec29a354336143c3c1ca1b90db0669031e1790
Timestamp: 1742050045 Timestamp [UCT]: 2025-03-15 14:47:25 Age [y:d:h:m:s]: 00:296:09:46:36
Block: 1239909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209646 RingCT/type: yes/0
Extra: 016e5ac557ae6c15ac24c0296b9eec29a354336143c3c1ca1b90db0669031e17900211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24ac3d659df693ff6d61756135e5bcf31483ae25e630a8f5b802bcaf3b19c245 0.600000000000 1726874 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": 1239919, "vin": [ { "gen": { "height": 1239909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24ac3d659df693ff6d61756135e5bcf31483ae25e630a8f5b802bcaf3b19c245" } } ], "extra": [ 1, 110, 90, 197, 87, 174, 108, 21, 172, 36, 192, 41, 107, 158, 236, 41, 163, 84, 51, 97, 67, 195, 193, 202, 27, 144, 219, 6, 105, 3, 30, 23, 144, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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