Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf1e74aafe2422ab796f060d9aed651b66eba2bfe743e7f4d9d5918813e8e767

Tx prefix hash: b86bac66603373fc8552068d6e5bf7cac8c488f5685c8766c43b3417d8250aa8
Tx public key: 15e87807d55d625f7bcf966149fd22ad6aee9f9490af9cd65dec62be92702518
Timestamp: 1720863074 Timestamp [UCT]: 2024-07-13 09:31:14 Age [y:d:h:m:s]: 00:181:19:22:25
Block: 1064724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130075 RingCT/type: yes/0
Extra: 0115e87807d55d625f7bcf966149fd22ad6aee9f9490af9cd65dec62be9270251802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06f2e9e6aeaf6b36ba8e42d6e5c1c735c3b8697ffb94ea9bffc1f2955db3df34 0.600000000000 1535259 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": 1064734, "vin": [ { "gen": { "height": 1064724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06f2e9e6aeaf6b36ba8e42d6e5c1c735c3b8697ffb94ea9bffc1f2955db3df34" } } ], "extra": [ 1, 21, 232, 120, 7, 213, 93, 98, 95, 123, 207, 150, 97, 73, 253, 34, 173, 106, 238, 159, 148, 144, 175, 156, 214, 93, 236, 98, 190, 146, 112, 37, 24, 2, 17, 0, 0, 0, 1, 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