Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44df3ed377dc1d23e58814980e17f2025e0ef940a6a9b77a6ed84213aa1ab6c9

Tx prefix hash: 2c5c7d6a3b64c2b8bba817ee77523ad731a7b6f9ab9f31a486a1c0350dcad906
Tx public key: 0f548cb95070e1a01b6d9907ef9e47a952d7701a462ca55a3f5d24250f7fe2d9
Timestamp: 1582127199 Timestamp [UCT]: 2020-02-19 15:46:39 Age [y:d:h:m:s]: 04:352:09:11:04
Block: 68214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1144075 RingCT/type: yes/0
Extra: 010f548cb95070e1a01b6d9907ef9e47a952d7701a462ca55a3f5d24250f7fe2d9021100000002724f989b000000000000000000

1 output(s) for total of 364.736735999000 dcy

stealth address amount amount idx
00: 8d30fe8322890cea1fffb08446f8348678ac5d3f6071e1a31cc7f10ec63a26d6 364.736735999000 125718 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": 68224, "vin": [ { "gen": { "height": 68214 } } ], "vout": [ { "amount": 364736735999, "target": { "key": "8d30fe8322890cea1fffb08446f8348678ac5d3f6071e1a31cc7f10ec63a26d6" } } ], "extra": [ 1, 15, 84, 140, 185, 80, 112, 225, 160, 27, 109, 153, 7, 239, 158, 71, 169, 82, 215, 112, 26, 70, 44, 165, 90, 63, 93, 36, 37, 15, 127, 226, 217, 2, 17, 0, 0, 0, 2, 114, 79, 152, 155, 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