Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56976cbf0d3e4e6af3b322ecc9d924f9ea6a9e259444c96397c914f1627a29f9

Tx prefix hash: 8b3712367449bc1fd82560c521bcb3aa94b2b8e047a675d8b526077466db3f7e
Tx public key: f4e3ae8b9206dbf449ffd594322f2c017d8cbe0f033e17e781af1128636093cb
Timestamp: 1710517967 Timestamp [UCT]: 2024-03-15 15:52:47 Age [y:d:h:m:s]: 01:025:18:26:48
Block: 978966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279384 RingCT/type: yes/0
Extra: 01f4e3ae8b9206dbf449ffd594322f2c017d8cbe0f033e17e781af1128636093cb02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5044d203edf0021e69a0c282d511ff243fc08648d975ee1097784c5ec7b3be1c 0.600000000000 1438995 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": 978976, "vin": [ { "gen": { "height": 978966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5044d203edf0021e69a0c282d511ff243fc08648d975ee1097784c5ec7b3be1c" } } ], "extra": [ 1, 244, 227, 174, 139, 146, 6, 219, 244, 73, 255, 213, 148, 50, 47, 44, 1, 125, 140, 190, 15, 3, 62, 23, 231, 129, 175, 17, 40, 99, 96, 147, 203, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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