Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d808af621700788355d3a961e6bc989982abdbc97bdf5fc30d5bdee13957ecbd

Tx prefix hash: 43186a30e068f269f84f168b6a9f4f6cff5e8056633f3d13bda86dca65b4c4a0
Tx public key: ed89cb082cc8df913fc4c3c8261eac7392f7436dad1eebf8276b119e4424ae79
Timestamp: 1733294311 Timestamp [UCT]: 2024-12-04 06:38:31 Age [y:d:h:m:s]: 00:110:08:17:02
Block: 1167672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78659 RingCT/type: yes/0
Extra: 01ed89cb082cc8df913fc4c3c8261eac7392f7436dad1eebf8276b119e4424ae790211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 034c21c098d5dad29f8429efb5aa919eed5390580ff108289d0c6768ba4d411f 0.600000000000 1653371 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": 1167682, "vin": [ { "gen": { "height": 1167672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "034c21c098d5dad29f8429efb5aa919eed5390580ff108289d0c6768ba4d411f" } } ], "extra": [ 1, 237, 137, 203, 8, 44, 200, 223, 145, 63, 196, 195, 200, 38, 30, 172, 115, 146, 247, 67, 109, 173, 30, 235, 248, 39, 107, 17, 158, 68, 36, 174, 121, 2, 17, 0, 0, 0, 4, 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