Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 969c250a0f23b21c6bddf63da018d89a59aa2989a0dc0d6b9b57f573dbbc9eb5

Tx prefix hash: 4f716f2c9f4d6f33a298f217ebbf32462800674b0f72716536cd5155150cc1c7
Tx public key: f0d35904102916f90c81c9026a44c0e7b4812d09ffa0df9e220b97477422ec6f
Timestamp: 1729797329 Timestamp [UCT]: 2024-10-24 19:15:29 Age [y:d:h:m:s]: 00:187:22:51:08
Block: 1138741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134146 RingCT/type: yes/0
Extra: 01f0d35904102916f90c81c9026a44c0e7b4812d09ffa0df9e220b97477422ec6f021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c98f5ac44ee2aad51d47879604a040059c19e175feefb7eb7212b4097e1c493 0.600000000000 1622454 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": 1138751, "vin": [ { "gen": { "height": 1138741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c98f5ac44ee2aad51d47879604a040059c19e175feefb7eb7212b4097e1c493" } } ], "extra": [ 1, 240, 211, 89, 4, 16, 41, 22, 249, 12, 129, 201, 2, 106, 68, 192, 231, 180, 129, 45, 9, 255, 160, 223, 158, 34, 11, 151, 71, 116, 34, 236, 111, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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