Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f84c3cbcff3a9dd9256853b135f42d37ec47000f3277a3b92790328851e3053

Tx prefix hash: 436a263ec651be3a1d4ee18cdc1f079d00fcc354c3ff97acdc8cde1b5a23a615
Tx public key: 5db2d1b422d8cea68200b6bec76e8cc44fd1d67e6cc2e80caaf8b6c1b7f0a7a9
Timestamp: 1631112898 Timestamp [UCT]: 2021-09-08 14:54:58 Age [y:d:h:m:s]: 03:179:19:04:57
Block: 329858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 903460 RingCT/type: yes/0
Extra: 015db2d1b422d8cea68200b6bec76e8cc44fd1d67e6cc2e80caaf8b6c1b7f0a7a9021100000053fdc024ec000000000000000000

1 output(s) for total of 49.550034611000 dcy

stealth address amount amount idx
00: 860e531b661e1cd966dfef9094886bf1406650359431e022cf439eae04df7bc9 49.550034611000 682205 of 0

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": 329868, "vin": [ { "gen": { "height": 329858 } } ], "vout": [ { "amount": 49550034611, "target": { "key": "860e531b661e1cd966dfef9094886bf1406650359431e022cf439eae04df7bc9" } } ], "extra": [ 1, 93, 178, 209, 180, 34, 216, 206, 166, 130, 0, 182, 190, 199, 110, 140, 196, 79, 209, 214, 126, 108, 194, 232, 12, 170, 248, 182, 193, 183, 240, 167, 169, 2, 17, 0, 0, 0, 83, 253, 192, 36, 236, 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