Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 223a376777b9634dc341adc56a7600ad8a8d5d3b65041aff049faa7dc02207a2

Tx prefix hash: 5cadb56752c92ead1d2cf63c85b930af1b03e9dbef7e7928fb5031090a8d46b9
Tx public key: f10c10f8b691124ae5987c592db752bd31426c887a8032a5cfea5ae8e1a08918
Timestamp: 1581824741 Timestamp [UCT]: 2020-02-16 03:45:41 Age [y:d:h:m:s]: 04:284:16:43:41
Block: 66071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1095566 RingCT/type: yes/0
Extra: 01f10c10f8b691124ae5987c592db752bd31426c887a8032a5cfea5ae8e1a089180211000000037adf42d3000000000000000000

1 output(s) for total of 370.749145770000 dcy

stealth address amount amount idx
00: d7a0af069e2f6d6f4cc0381509b2eecd099ff21919831e4dfb4d6aa3f9bdd769 370.749145770000 121720 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": 66081, "vin": [ { "gen": { "height": 66071 } } ], "vout": [ { "amount": 370749145770, "target": { "key": "d7a0af069e2f6d6f4cc0381509b2eecd099ff21919831e4dfb4d6aa3f9bdd769" } } ], "extra": [ 1, 241, 12, 16, 248, 182, 145, 18, 74, 229, 152, 124, 89, 45, 183, 82, 189, 49, 66, 108, 136, 122, 128, 50, 165, 207, 234, 90, 232, 225, 160, 137, 24, 2, 17, 0, 0, 0, 3, 122, 223, 66, 211, 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