Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9a63872dd447a68f6cd4b378c72760c04b9fa95c8e729184de4d0e622ba357d

Tx prefix hash: 1fdc8244388ef38cd87e5c8d14c91a8835aa86dcddcc567cc10cb5f21f60b2f5
Tx public key: 16d121e0f4d053f73de38375333c2d9a972e92b53bbe4b89eefd54ca25c9d516
Timestamp: 1582022855 Timestamp [UCT]: 2020-02-18 10:47:35 Age [y:d:h:m:s]: 05:084:18:58:19
Block: 67326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1213777 RingCT/type: yes/0
Extra: 0116d121e0f4d053f73de38375333c2d9a972e92b53bbe4b89eefd54ca25c9d51602110000000112c4732d000000000000000000

1 output(s) for total of 367.216190773000 dcy

stealth address amount amount idx
00: 26a9f9ac8601ec160b146138165e6f202fa9e4012713a9ad4788cd63083bcaaf 367.216190773000 124090 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": 67336, "vin": [ { "gen": { "height": 67326 } } ], "vout": [ { "amount": 367216190773, "target": { "key": "26a9f9ac8601ec160b146138165e6f202fa9e4012713a9ad4788cd63083bcaaf" } } ], "extra": [ 1, 22, 209, 33, 224, 244, 208, 83, 247, 61, 227, 131, 117, 51, 60, 45, 154, 151, 46, 146, 181, 59, 190, 75, 137, 238, 253, 84, 202, 37, 201, 213, 22, 2, 17, 0, 0, 0, 1, 18, 196, 115, 45, 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