Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62dab374cc82a586be8d820f8f51f780f44851d34327378e5d6014f0ee257117

Tx prefix hash: bae9c71f409535a3a534ae76de413d8835d56d1751f9f97353236cb5e79b1bcb
Tx public key: 7797a03ed99df61c61132b3fe7e72b22c014b9b7f797d8ec64dc8968042ae17d
Timestamp: 1706237875 Timestamp [UCT]: 2024-01-26 02:57:55 Age [y:d:h:m:s]: 01:076:01:57:38
Block: 943427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315485 RingCT/type: yes/0
Extra: 017797a03ed99df61c61132b3fe7e72b22c014b9b7f797d8ec64dc8968042ae17d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0468bf03663144209eddf80ae362a81b2b505c681e523c6469fa9fe01392563 0.600000000000 1401633 of 15

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": 943437, "vin": [ { "gen": { "height": 943427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0468bf03663144209eddf80ae362a81b2b505c681e523c6469fa9fe01392563" } } ], "extra": [ 1, 119, 151, 160, 62, 217, 157, 246, 28, 97, 19, 43, 63, 231, 231, 43, 34, 192, 20, 185, 183, 247, 151, 216, 236, 100, 220, 137, 104, 4, 42, 225, 125, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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