Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3526aa58e6cf55e8c9dd38e9f988f26a2ed3d3658f25c43f472d18a4c6776b91

Tx prefix hash: 36d86a8e093711917a97cc7d406a1702e158feee6106d79602cc71cfe75208e8
Tx public key: 8fbfeb58eb7afcdf252bb8a673f6a348a90699e9a7d73c2cbf46504aa3aff900
Timestamp: 1734325466 Timestamp [UCT]: 2024-12-16 05:04:26 Age [y:d:h:m:s]: 00:102:03:02:26
Block: 1176230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72753 RingCT/type: yes/0
Extra: 018fbfeb58eb7afcdf252bb8a673f6a348a90699e9a7d73c2cbf46504aa3aff9000211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad2c1317965a6a1babee7dfee51f88c5674f19f03d515295051b43c2753d6a1b 0.600000000000 1662561 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": 1176240, "vin": [ { "gen": { "height": 1176230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad2c1317965a6a1babee7dfee51f88c5674f19f03d515295051b43c2753d6a1b" } } ], "extra": [ 1, 143, 191, 235, 88, 235, 122, 252, 223, 37, 43, 184, 166, 115, 246, 163, 72, 169, 6, 153, 233, 167, 215, 60, 44, 191, 70, 80, 74, 163, 175, 249, 0, 2, 17, 0, 0, 0, 6, 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