Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83f42c6f2d04c5bd1b40b94c233caef0daa5039ca87ef8f2df3e4d648db93d42

Tx prefix hash: d7e11c5ecfe0513c12cb0c81b34554f827213f61d24282c2d3bba7c596f4912e
Tx public key: 388eeec6c9f1ccd0a24f5dfd6fa867ab840bf0efd1713ba0895c3bcd4e89addf
Timestamp: 1577661298 Timestamp [UCT]: 2019-12-29 23:14:58 Age [y:d:h:m:s]: 05:066:04:50:55
Block: 34601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1197098 RingCT/type: yes/0
Extra: 01388eeec6c9f1ccd0a24f5dfd6fa867ab840bf0efd1713ba0895c3bcd4e89addf0211000000094ac5aa02000000000000000000

1 output(s) for total of 471.360709625000 dcy

stealth address amount amount idx
00: c689452c24d4e87228d80941e86f5c1fb91a14e994df41946bb055e1acc69a24 471.360709625000 58271 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": 34611, "vin": [ { "gen": { "height": 34601 } } ], "vout": [ { "amount": 471360709625, "target": { "key": "c689452c24d4e87228d80941e86f5c1fb91a14e994df41946bb055e1acc69a24" } } ], "extra": [ 1, 56, 142, 238, 198, 201, 241, 204, 208, 162, 79, 93, 253, 111, 168, 103, 171, 132, 11, 240, 239, 209, 113, 59, 160, 137, 92, 59, 205, 78, 137, 173, 223, 2, 17, 0, 0, 0, 9, 74, 197, 170, 2, 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