Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f714a4cc9b5936d52b3e3dd47887736a1554d23fb038556c7b4168340406c83

Tx prefix hash: 35fa9808acec44aadc37e09fce5b2f344801c1d81e702cd3f5cc381daef895c3
Tx public key: c711a6c42b9e2c0778a2b99aa2f3dbc3fc64d3e46c851a1d81691589e2aa0415
Timestamp: 1625701102 Timestamp [UCT]: 2021-07-07 23:38:22 Age [y:d:h:m:s]: 03:142:01:06:26
Block: 289986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 871780 RingCT/type: yes/0
Extra: 01c711a6c42b9e2c0778a2b99aa2f3dbc3fc64d3e46c851a1d81691589e2aa04150211000000294b22f71d000000000000000000

1 output(s) for total of 67.167086174000 dcy

stealth address amount amount idx
00: fe6faeed81439c88fc0bbebf7abf3e9e44a2ec3790d9a09d6c484930376734a9 67.167086174000 607462 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": 289996, "vin": [ { "gen": { "height": 289986 } } ], "vout": [ { "amount": 67167086174, "target": { "key": "fe6faeed81439c88fc0bbebf7abf3e9e44a2ec3790d9a09d6c484930376734a9" } } ], "extra": [ 1, 199, 17, 166, 196, 43, 158, 44, 7, 120, 162, 185, 154, 162, 243, 219, 195, 252, 100, 211, 228, 108, 133, 26, 29, 129, 105, 21, 137, 226, 170, 4, 21, 2, 17, 0, 0, 0, 41, 75, 34, 247, 29, 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