Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 877ae9d91301bdda7b313c14da43b31f80a6efbe41640c311582a89c0d6471d3

Tx prefix hash: bb53ef34f69eda9a9d41141b83ba296353b38a024599113b7feca0f61e34ee97
Tx public key: eb9735f4d0c72cd5e8c1c6792a7f041758ed0acad62efc3323225944b3a8bfb9
Timestamp: 1722444019 Timestamp [UCT]: 2024-07-31 16:40:19 Age [y:d:h:m:s]: 00:228:19:37:12
Block: 1077814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163451 RingCT/type: yes/0
Extra: 01eb9735f4d0c72cd5e8c1c6792a7f041758ed0acad62efc3323225944b3a8bfb902110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ccbdcf20b5d76736c3abd9430658e1b10e41fdfc05b6216fb432dcdfa985623 0.600000000000 1550369 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": 1077824, "vin": [ { "gen": { "height": 1077814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ccbdcf20b5d76736c3abd9430658e1b10e41fdfc05b6216fb432dcdfa985623" } } ], "extra": [ 1, 235, 151, 53, 244, 208, 199, 44, 213, 232, 193, 198, 121, 42, 127, 4, 23, 88, 237, 10, 202, 214, 46, 252, 51, 35, 34, 89, 68, 179, 168, 191, 185, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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