Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dfcf258289a98e79851fb4060bde8a76b404692d784125743cb51a2f1e07a0c

Tx prefix hash: fcd9621f1b75607e6add24b791f7a000c69d43d79054c8cbd746afa8d910cd91
Tx public key: 3c7f13a932b1903c75599384f2b3597f1da4da0d82e7e0b53474084896ab60ba
Timestamp: 1758841696 Timestamp [UCT]: 2025-09-25 23:08:16 Age [y:d:h:m:s]: 00:062:11:11:11
Block: 1376458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44731 RingCT/type: yes/0
Extra: 013c7f13a932b1903c75599384f2b3597f1da4da0d82e7e0b53474084896ab60ba02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 565a5176638a06b3f95b3eba8e1916bd67be079f4cff3de88ff74c0495ede1c8 0.600000000000 1864549 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": 1376468, "vin": [ { "gen": { "height": 1376458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "565a5176638a06b3f95b3eba8e1916bd67be079f4cff3de88ff74c0495ede1c8" } } ], "extra": [ 1, 60, 127, 19, 169, 50, 177, 144, 60, 117, 89, 147, 132, 242, 179, 89, 127, 29, 164, 218, 13, 130, 231, 224, 181, 52, 116, 8, 72, 150, 171, 96, 186, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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