Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec68719d0e23626c547504fd8cf1c9466343411a06b34b3a32a7393e040be364

Tx prefix hash: 58b76bb530243b02cff5cf8d65c4e9158db0d4e3ec5c0fac826968f9fdbcdd48
Tx public key: 95c2febbd11e2ad5a1000cef296bb9ba137e2f467564f2a65c02ea745f224700
Timestamp: 1705188325 Timestamp [UCT]: 2024-01-13 23:25:25 Age [y:d:h:m:s]: 01:086:19:14:26
Block: 934746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323133 RingCT/type: yes/0
Extra: 0195c2febbd11e2ad5a1000cef296bb9ba137e2f467564f2a65c02ea745f2247000211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac626f2fdc47420b44de7d0ceb49e268480f32dfa1d7a904ddd5e8a9e652bc0d 0.600000000000 1392762 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": 934756, "vin": [ { "gen": { "height": 934746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac626f2fdc47420b44de7d0ceb49e268480f32dfa1d7a904ddd5e8a9e652bc0d" } } ], "extra": [ 1, 149, 194, 254, 187, 209, 30, 42, 213, 161, 0, 12, 239, 41, 107, 185, 186, 19, 126, 47, 70, 117, 100, 242, 166, 92, 2, 234, 116, 95, 34, 71, 0, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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