Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0b7ac40790fc560e3f89b25893bda7708dc0538b55143c9e3a9b884f13a1fbc

Tx prefix hash: d3c6833e2c90fa47379eb70eeb2725f6109727256a6b28c4d1233b232968036d
Tx public key: b8fc99d2c47940b7a4df4df2667d5e83d8de3341e115df68a9857074230a8721
Timestamp: 1644277159 Timestamp [UCT]: 2022-02-07 23:39:19 Age [y:d:h:m:s]: 03:078:07:48:43
Block: 434110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 835601 RingCT/type: yes/0
Extra: 01b8fc99d2c47940b7a4df4df2667d5e83d8de3341e115df68a9857074230a872102110000000a4da16a3a000000000000000000

1 output(s) for total of 22.367305237000 dcy

stealth address amount amount idx
00: c9ed016e7cc7451030bc7b8492ff6424193f70de20bc95118fe3f45b8d5d507a 22.367305237000 844991 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": 434120, "vin": [ { "gen": { "height": 434110 } } ], "vout": [ { "amount": 22367305237, "target": { "key": "c9ed016e7cc7451030bc7b8492ff6424193f70de20bc95118fe3f45b8d5d507a" } } ], "extra": [ 1, 184, 252, 153, 210, 196, 121, 64, 183, 164, 223, 77, 242, 102, 125, 94, 131, 216, 222, 51, 65, 225, 21, 223, 104, 169, 133, 112, 116, 35, 10, 135, 33, 2, 17, 0, 0, 0, 10, 77, 161, 106, 58, 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