Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f69dc8edb69a1c134019dc14648149154c180d5300619dd1e5d4b10c84771ac

Tx prefix hash: 333aa87a39aef3bb5c90647b49f02e30fc2bbee33ccdf04fda5b3525f9f45da2
Tx public key: b79c780be9274feefe9b458a2a363c4f8f292a90cf83857dc6366d1631e1f24a
Timestamp: 1708855136 Timestamp [UCT]: 2024-02-25 09:58:56 Age [y:d:h:m:s]: 01:088:23:42:46
Block: 965164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324654 RingCT/type: yes/0
Extra: 01b79c780be9274feefe9b458a2a363c4f8f292a90cf83857dc6366d1631e1f24a02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa483841b80508dce75353a7d57854473ee65d99d72a880cf85b4b14d7578fc2 0.600000000000 1424913 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": 965174, "vin": [ { "gen": { "height": 965164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa483841b80508dce75353a7d57854473ee65d99d72a880cf85b4b14d7578fc2" } } ], "extra": [ 1, 183, 156, 120, 11, 233, 39, 79, 238, 254, 155, 69, 138, 42, 54, 60, 79, 143, 41, 42, 144, 207, 131, 133, 125, 198, 54, 109, 22, 49, 225, 242, 74, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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