Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76b1c6693e7f35a6b66f1976288b6da48394fb4b707565498610c2fa9d38f483

Tx prefix hash: 84b1c126caeb59514f43213ec02e33771b96a6bd0b685d8191a7a3b51fa25661
Tx public key: 487d90a2f3893636a5e90005f9fe13775a0727e9f01f5c5d1f1a05ec5376d60e
Timestamp: 1705825269 Timestamp [UCT]: 2024-01-21 08:21:09 Age [y:d:h:m:s]: 01:087:20:48:41
Block: 940003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323916 RingCT/type: yes/0
Extra: 01487d90a2f3893636a5e90005f9fe13775a0727e9f01f5c5d1f1a05ec5376d60e0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 161ccd6cfad9c986427fa1fc1ecf67960e822e6f267d2acedbf5918a1623fa57 0.600000000000 1398137 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": 940013, "vin": [ { "gen": { "height": 940003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "161ccd6cfad9c986427fa1fc1ecf67960e822e6f267d2acedbf5918a1623fa57" } } ], "extra": [ 1, 72, 125, 144, 162, 243, 137, 54, 54, 165, 233, 0, 5, 249, 254, 19, 119, 90, 7, 39, 233, 240, 31, 92, 93, 31, 26, 5, 236, 83, 118, 214, 14, 2, 17, 0, 0, 0, 2, 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