Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00064307407cc09bb573cbf066dfdaa7cc6ea9d372a7d816faeb00c9e81f936e

Tx prefix hash: 6585569e32a6f66c29f455d82fef1542ca630eac19c2fcaec0fa8cc515adf4f0
Tx public key: 063a73d3cd8bae11781c695e934f0521758496c993193c6f973f67e3354c9bf3
Timestamp: 1754480405 Timestamp [UCT]: 2025-08-06 11:40:05 Age [y:d:h:m:s]: 00:106:16:24:03
Block: 1341441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75251 RingCT/type: yes/0
Extra: 01063a73d3cd8bae11781c695e934f0521758496c993193c6f973f67e3354c9bf3021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3997058429562a54114731064dae15f8a4c0f28ce56b89a7282cc9fc532a04e8 0.600000000000 1829266 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": 1341451, "vin": [ { "gen": { "height": 1341441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3997058429562a54114731064dae15f8a4c0f28ce56b89a7282cc9fc532a04e8" } } ], "extra": [ 1, 6, 58, 115, 211, 205, 139, 174, 17, 120, 28, 105, 94, 147, 79, 5, 33, 117, 132, 150, 201, 147, 25, 60, 111, 151, 63, 103, 227, 53, 76, 155, 243, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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