Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b83c7d95e6830e1439b4456e1bc6348dfef5ae4cb13862c7b1aacf8f5a6341b0

Tx prefix hash: 96e80044be37c04c7c205a0cee17f7f0cec7fb04fc649c7d7edea4ee5494a389
Tx public key: 5b51f8777d1375b4fba31b1da3b1cdb87c04a0bf8ba6ee5762d30c076e1ff054
Timestamp: 1577046652 Timestamp [UCT]: 2019-12-22 20:30:52 Age [y:d:h:m:s]: 05:016:12:06:43
Block: 29734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161612 RingCT/type: yes/0
Extra: 015b51f8777d1375b4fba31b1da3b1cdb87c04a0bf8ba6ee5762d30c076e1ff0540211000000078a2ee0d9000000000000000000

1 output(s) for total of 489.192485837000 dcy

stealth address amount amount idx
00: d3cc48ce146468589614800ae6654a16f10c0f380cf5912aefd8c62623bcd248 489.192485837000 48974 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": 29744, "vin": [ { "gen": { "height": 29734 } } ], "vout": [ { "amount": 489192485837, "target": { "key": "d3cc48ce146468589614800ae6654a16f10c0f380cf5912aefd8c62623bcd248" } } ], "extra": [ 1, 91, 81, 248, 119, 125, 19, 117, 180, 251, 163, 27, 29, 163, 177, 205, 184, 124, 4, 160, 191, 139, 166, 238, 87, 98, 211, 12, 7, 110, 31, 240, 84, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 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