Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38c553f8f5f3a747b70ba3f9f84aedae821d30cf119dd6065c5fd9e83a4e47fc

Tx prefix hash: cc02f19e7516aaff6b0be0ecf1e3422a5cb05fc6a4f7c33bee0bb4e87bf92aba
Tx public key: f8baaa6d9265294776b7ecd51cf55cb129eee42754eba372d13541494b54b6a1
Timestamp: 1746245620 Timestamp [UCT]: 2025-05-03 04:13:40 Age [y:d:h:m:s]: 00:245:17:32:04
Block: 1274619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173412 RingCT/type: yes/0
Extra: 01f8baaa6d9265294776b7ecd51cf55cb129eee42754eba372d13541494b54b6a1021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9408a3c36ac2b37e5c0ab910cbbeb184a2721163c28cb29c1fb4d1b65264588d 0.600000000000 1761914 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": 1274629, "vin": [ { "gen": { "height": 1274619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9408a3c36ac2b37e5c0ab910cbbeb184a2721163c28cb29c1fb4d1b65264588d" } } ], "extra": [ 1, 248, 186, 170, 109, 146, 101, 41, 71, 118, 183, 236, 213, 28, 245, 92, 177, 41, 238, 228, 39, 84, 235, 163, 114, 209, 53, 65, 73, 75, 84, 182, 161, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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