Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fee32cc08d44840a21751ce12db8f0ffbf3ef2e790bd1139eb9e9c5dd312793

Tx prefix hash: fc72cd514668f410e8c09364cc06537b0b452cfcef2dadf19867316ddd3c9670
Tx public key: 9a21cb88e68739d852accbf5d64002b00125fe6db3bce4bef1fc39599eee524f
Timestamp: 1650157344 Timestamp [UCT]: 2022-04-17 01:02:24 Age [y:d:h:m:s]: 02:228:06:19:24
Block: 481786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 683046 RingCT/type: yes/0
Extra: 019a21cb88e68739d852accbf5d64002b00125fe6db3bce4bef1fc39599eee524f021100000007bf7ee4e7000000000000000000

1 output(s) for total of 15.546878886000 dcy

stealth address amount amount idx
00: 573cee4c038bec567b7120a7b5a1dd45a11c7ecfdc8c018cb1dd880cf271b9e9 15.546878886000 903129 of 0

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": 481796, "vin": [ { "gen": { "height": 481786 } } ], "vout": [ { "amount": 15546878886, "target": { "key": "573cee4c038bec567b7120a7b5a1dd45a11c7ecfdc8c018cb1dd880cf271b9e9" } } ], "extra": [ 1, 154, 33, 203, 136, 230, 135, 57, 216, 82, 172, 203, 245, 214, 64, 2, 176, 1, 37, 254, 109, 179, 188, 228, 190, 241, 252, 57, 89, 158, 238, 82, 79, 2, 17, 0, 0, 0, 7, 191, 126, 228, 231, 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