Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc13210d7b083cb50c2abad8d2997f7995af50f625d5bc00fba74533424e3272

Tx prefix hash: bc57e360a80f36067120fdc1f70145dd5d40ef7ef9b3a3c793c1bfd1de6713da
Tx public key: 73d6945f10e56351d87620dc51d4aea376d73cd91a297c5f1f81dbeb78c95bf4
Timestamp: 1752932654 Timestamp [UCT]: 2025-07-19 13:44:14 Age [y:d:h:m:s]: 00:122:19:54:03
Block: 1328863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86569 RingCT/type: yes/0
Extra: 0173d6945f10e56351d87620dc51d4aea376d73cd91a297c5f1f81dbeb78c95bf4021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf425c1fc296bd5ad8d7e5384bcd9490877f3f839904bcfa33474294d65527f6 0.600000000000 1816636 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": 1328873, "vin": [ { "gen": { "height": 1328863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf425c1fc296bd5ad8d7e5384bcd9490877f3f839904bcfa33474294d65527f6" } } ], "extra": [ 1, 115, 214, 148, 95, 16, 229, 99, 81, 216, 118, 32, 220, 81, 212, 174, 163, 118, 215, 60, 217, 26, 41, 124, 95, 31, 129, 219, 235, 120, 201, 91, 244, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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