Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a89973c4e5186f8f42707f0893d1cb8afac7de6b8c28a7b77eedf9c78faa817e

Tx prefix hash: 11969a226ad6c3754c61e57c8cb29b98e42ed0ae3928b7a6f29c85e4b0f93100
Tx public key: bf15b901612ff7ce3fde6b1574346d6e80e5b772f7bf69696ddfc949720acea9
Timestamp: 1722018797 Timestamp [UCT]: 2024-07-26 18:33:17 Age [y:d:h:m:s]: 00:308:06:06:16
Block: 1074283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220270 RingCT/type: yes/0
Extra: 01bf15b901612ff7ce3fde6b1574346d6e80e5b772f7bf69696ddfc949720acea9021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efc0e73ed701775a4c07057223e2102fa213df7b63a72af7c2c2ba980de534a4 0.600000000000 1546796 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": 1074293, "vin": [ { "gen": { "height": 1074283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efc0e73ed701775a4c07057223e2102fa213df7b63a72af7c2c2ba980de534a4" } } ], "extra": [ 1, 191, 21, 185, 1, 97, 47, 247, 206, 63, 222, 107, 21, 116, 52, 109, 110, 128, 229, 183, 114, 247, 191, 105, 105, 109, 223, 201, 73, 114, 10, 206, 169, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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