Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23a671e6c5b7cb2b8abe680d88b821fb2e692a7634009bed3fa35f41f03edb67

Tx prefix hash: f00ab2d7bf8a1ccff9af9b9f73092c713b69a90220c6e5caed0b5219b10b182b
Tx public key: 76550951888a0168cda7537f3f6ee60b87b8e957004074010bec42448b39fc92
Timestamp: 1644426667 Timestamp [UCT]: 2022-02-09 17:11:07 Age [y:d:h:m:s]: 02:349:13:36:05
Block: 435111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 769003 RingCT/type: yes/0
Extra: 0176550951888a0168cda7537f3f6ee60b87b8e957004074010bec42448b39fc92021100000006d3fcec30000000000000000000

1 output(s) for total of 22.197135564000 dcy

stealth address amount amount idx
00: 935ecd399c30a3b1bbdbd0004f1b27d40dc2aa52a977540416dfa865f06f4fb1 22.197135564000 846204 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": 435121, "vin": [ { "gen": { "height": 435111 } } ], "vout": [ { "amount": 22197135564, "target": { "key": "935ecd399c30a3b1bbdbd0004f1b27d40dc2aa52a977540416dfa865f06f4fb1" } } ], "extra": [ 1, 118, 85, 9, 81, 136, 138, 1, 104, 205, 167, 83, 127, 63, 110, 230, 11, 135, 184, 233, 87, 0, 64, 116, 1, 11, 236, 66, 68, 139, 57, 252, 146, 2, 17, 0, 0, 0, 6, 211, 252, 236, 48, 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