Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbc2b4694016453eeffec89ece00f6e3c99a67f82b670486373f1cddea3b6579

Tx prefix hash: 05530cb16fd20b6662e0fcc4a838af91b9b6b6d5d113d88ca8f199cb0aa350dc
Tx public key: f8b1fd3879575f1ce4e5d02d0af4231a6419194adfe7e7d4b3a5166ee4419b7e
Timestamp: 1647641656 Timestamp [UCT]: 2022-03-18 22:14:16 Age [y:d:h:m:s]: 03:227:06:22:15
Block: 461382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 940319 RingCT/type: yes/0
Extra: 01f8b1fd3879575f1ce4e5d02d0af4231a6419194adfe7e7d4b3a5166ee4419b7e021100000001bf7ee4e7000000000000000000

1 output(s) for total of 18.167937583000 dcy

stealth address amount amount idx
00: 096af2cc54eb5ffbe93d916ec81feeeae91991335b1dd86d4782290c315fd0d8 18.167937583000 878609 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": 461392, "vin": [ { "gen": { "height": 461382 } } ], "vout": [ { "amount": 18167937583, "target": { "key": "096af2cc54eb5ffbe93d916ec81feeeae91991335b1dd86d4782290c315fd0d8" } } ], "extra": [ 1, 248, 177, 253, 56, 121, 87, 95, 28, 228, 229, 208, 45, 10, 244, 35, 26, 100, 25, 25, 74, 223, 231, 231, 212, 179, 165, 22, 110, 228, 65, 155, 126, 2, 17, 0, 0, 0, 1, 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