Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4358d00412f1b53c87823c677f418cd4c195b9d3ad51f711f33521b382261070

Tx prefix hash: 4f57c21c232a00af50b6b62fa3e86f19ff268fab8e7a42b71facec9403d167a0
Tx public key: 977b1f34c884e109f719c30b0ccc01b5c555ca3ce197cad07fff345a793bd9ae
Timestamp: 1644562176 Timestamp [UCT]: 2022-02-11 06:49:36 Age [y:d:h:m:s]: 02:363:12:29:27
Block: 436156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 778838 RingCT/type: yes/0
Extra: 01977b1f34c884e109f719c30b0ccc01b5c555ca3ce197cad07fff345a793bd9ae0211000000102e6b1fd5000000000000000000

1 output(s) for total of 22.020867009000 dcy

stealth address amount amount idx
00: 0ccceff5676cc7d1f9d61bba97ce8685fd33dd3eee4936354a643b177a641bc3 22.020867009000 847475 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": 436166, "vin": [ { "gen": { "height": 436156 } } ], "vout": [ { "amount": 22020867009, "target": { "key": "0ccceff5676cc7d1f9d61bba97ce8685fd33dd3eee4936354a643b177a641bc3" } } ], "extra": [ 1, 151, 123, 31, 52, 200, 132, 225, 9, 247, 25, 195, 11, 12, 204, 1, 181, 197, 85, 202, 60, 225, 151, 202, 208, 127, 255, 52, 90, 121, 59, 217, 174, 2, 17, 0, 0, 0, 16, 46, 107, 31, 213, 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