Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba4d81a9e471b627829707c0c9379e5d14f5afa587da8c1e22411f451e7f73bf

Tx prefix hash: 7b8ee783693c733e2506a323eda745b336d0d474140aa22f2a8392d80c63be8c
Tx public key: 5bbd88780a800c7168d4e2365e48bc2d07402629fcc6d90b9e80b245d50b7622
Timestamp: 1729724186 Timestamp [UCT]: 2024-10-23 22:56:26 Age [y:d:h:m:s]: 00:031:08:54:53
Block: 1138145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22404 RingCT/type: yes/0
Extra: 015bbd88780a800c7168d4e2365e48bc2d07402629fcc6d90b9e80b245d50b7622021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42197ff64c8fcf67b21af585fdeeea44c0604e8849522d1d8a6437bd591b2342 0.600000000000 1621758 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": 1138155, "vin": [ { "gen": { "height": 1138145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42197ff64c8fcf67b21af585fdeeea44c0604e8849522d1d8a6437bd591b2342" } } ], "extra": [ 1, 91, 189, 136, 120, 10, 128, 12, 113, 104, 212, 226, 54, 94, 72, 188, 45, 7, 64, 38, 41, 252, 198, 217, 11, 158, 128, 178, 69, 213, 11, 118, 34, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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