Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16ba5518466c13417659ad5ec7e3275bf1d09f47fe3b60e508749a9ef4c277ec

Tx prefix hash: 72caf306c855e814f59015a61a1d8cd5efcbc490ddf6aaf1a19ec511c7a46b73
Tx public key: 4ba1862613bad533b27529020e8becca894c5c8bcedf4e647e0f6e1b1a874c73
Timestamp: 1723893000 Timestamp [UCT]: 2024-08-17 11:10:00 Age [y:d:h:m:s]: 01:092:03:00:40
Block: 1089841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324304 RingCT/type: yes/0
Extra: 014ba1862613bad533b27529020e8becca894c5c8bcedf4e647e0f6e1b1a874c7302110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 159ca0384c1a606da02189ce54dcac618d31a250c74efb3c4e6b7129300b9d48 0.600000000000 1564464 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": 1089851, "vin": [ { "gen": { "height": 1089841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "159ca0384c1a606da02189ce54dcac618d31a250c74efb3c4e6b7129300b9d48" } } ], "extra": [ 1, 75, 161, 134, 38, 19, 186, 213, 51, 178, 117, 41, 2, 14, 139, 236, 202, 137, 76, 92, 139, 206, 223, 78, 100, 126, 15, 110, 27, 26, 135, 76, 115, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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