Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd2dd106209ebe9ed10f4fe62b071f79e9c9d2c13911d583b609a4bc02e1ea56

Tx prefix hash: 70444e2c4c109c02f5fd56c20b627a4a38c6013069310e67ec29742f4c0f2e88
Tx public key: 5211ec49dfac926223f0ad95113d18a328463b2c4c895aaaefe5a22bb3c97496
Timestamp: 1713024959 Timestamp [UCT]: 2024-04-13 16:15:59 Age [y:d:h:m:s]: 01:064:13:36:41
Block: 999704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307048 RingCT/type: yes/0
Extra: 015211ec49dfac926223f0ad95113d18a328463b2c4c895aaaefe5a22bb3c9749602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c5bf6fa7b15c691c084be7e47e341013484b2f9e457242176be7b97b90c23f7 0.600000000000 1460186 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": 999714, "vin": [ { "gen": { "height": 999704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c5bf6fa7b15c691c084be7e47e341013484b2f9e457242176be7b97b90c23f7" } } ], "extra": [ 1, 82, 17, 236, 73, 223, 172, 146, 98, 35, 240, 173, 149, 17, 61, 24, 163, 40, 70, 59, 44, 76, 137, 90, 170, 239, 229, 162, 43, 179, 201, 116, 150, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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