Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf315c124f8eebaa4f73504b4178b20a003bf7811c67c13762234d1bc6820778

Tx prefix hash: 338d81b844094bdb2577559ce6fcf7818eebfb68bb99bf1cb86214f382de658d
Tx public key: dc43686f1f4cc65c4a22b3dfee292ec7eb1a9afce6d8befcc34c825a62c7b969
Timestamp: 1752755257 Timestamp [UCT]: 2025-07-17 12:27:37 Age [y:d:h:m:s]: 00:200:00:43:49
Block: 1327405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141659 RingCT/type: yes/0
Extra: 01dc43686f1f4cc65c4a22b3dfee292ec7eb1a9afce6d8befcc34c825a62c7b96902110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d5ac6a4f03ed9457e09712507f825be3df2e246d700881e454b85525bb9a588 0.600000000000 1815160 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": 1327415, "vin": [ { "gen": { "height": 1327405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d5ac6a4f03ed9457e09712507f825be3df2e246d700881e454b85525bb9a588" } } ], "extra": [ 1, 220, 67, 104, 111, 31, 76, 198, 92, 74, 34, 179, 223, 238, 41, 46, 199, 235, 26, 154, 252, 230, 216, 190, 252, 195, 76, 130, 90, 98, 199, 185, 105, 2, 17, 0, 0, 0, 4, 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