Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cde583e0b3adc002ed9b3faeeefeb6ba7a83f04cd9f57751c930f816e4f0474c

Tx prefix hash: b86bb38f4f63a8ae3fb623672bdeb041ec129440bfd3ebf5ef8d3477bdb2bc68
Tx public key: bac7fef77a932398627f279d68c5f1dcd684de5d284b73fd33c806fcedbae5dd
Timestamp: 1765031451 Timestamp [UCT]: 2025-12-06 14:30:51 Age [y:d:h:m:s]: 00:026:05:39:15
Block: 1427752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18792 RingCT/type: yes/0
Extra: 01bac7fef77a932398627f279d68c5f1dcd684de5d284b73fd33c806fcedbae5dd02110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c301edb7e84bdfc58b13d4e401d269a0975a79110a49a7d5c59c63f2ae89d85 0.600000000000 1916457 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": 1427762, "vin": [ { "gen": { "height": 1427752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c301edb7e84bdfc58b13d4e401d269a0975a79110a49a7d5c59c63f2ae89d85" } } ], "extra": [ 1, 186, 199, 254, 247, 122, 147, 35, 152, 98, 127, 39, 157, 104, 197, 241, 220, 214, 132, 222, 93, 40, 75, 115, 253, 51, 200, 6, 252, 237, 186, 229, 221, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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