Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90beb631d71451d15ad813f7b4ab6e703302990d6365d74e28fb75e6351eb228

Tx prefix hash: 88f85d4227a20c5460a2733482855c9b289aaa7a322b30376224bf25951fd664
Tx public key: f8b23a86f1c6db5fffce5892efa7283d3bd13e811bfbf91512b10bab38de1aee
Timestamp: 1705143911 Timestamp [UCT]: 2024-01-13 11:05:11 Age [y:d:h:m:s]: 01:115:11:56:43
Block: 934372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343675 RingCT/type: yes/0
Extra: 01f8b23a86f1c6db5fffce5892efa7283d3bd13e811bfbf91512b10bab38de1aee0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed6116bc39df49bb9dfbab4f424d1c7eea3873b6543e548e1d5c3163d3a4beca 0.600000000000 1392380 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": 934382, "vin": [ { "gen": { "height": 934372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed6116bc39df49bb9dfbab4f424d1c7eea3873b6543e548e1d5c3163d3a4beca" } } ], "extra": [ 1, 248, 178, 58, 134, 241, 198, 219, 95, 255, 206, 88, 146, 239, 167, 40, 61, 59, 209, 62, 129, 27, 251, 249, 21, 18, 177, 11, 171, 56, 222, 26, 238, 2, 17, 0, 0, 0, 4, 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