Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d585cb07f452fc7b67028f7f6f9f738cc03c3deaa215074bd2bf2f9e2bc8f6ef

Tx prefix hash: d54f64ed50e2dea7953714b68d408217f8a458b96416652c34c366df0c6cd530
Tx public key: 4390ecde2a1ee26b68d580efa42d6a41f61083fe15607db50101d9744bbaf3b4
Timestamp: 1734520484 Timestamp [UCT]: 2024-12-18 11:14:44 Age [y:d:h:m:s]: 00:125:16:27:32
Block: 1177854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89593 RingCT/type: yes/0
Extra: 014390ecde2a1ee26b68d580efa42d6a41f61083fe15607db50101d9744bbaf3b40211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fea07b25651dcc772c70c0ecbcb02f42430e86bb08f4d18e91e39e55b55cdd5 0.600000000000 1664231 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": 1177864, "vin": [ { "gen": { "height": 1177854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fea07b25651dcc772c70c0ecbcb02f42430e86bb08f4d18e91e39e55b55cdd5" } } ], "extra": [ 1, 67, 144, 236, 222, 42, 30, 226, 107, 104, 213, 128, 239, 164, 45, 106, 65, 246, 16, 131, 254, 21, 96, 125, 181, 1, 1, 217, 116, 75, 186, 243, 180, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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