Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3ce58583fede07be4af1a1a1d2d114c186a79ca4187c390125393cf029e2ea9

Tx prefix hash: a4a8fcbb3975e6fe6bbfbcfb08c948f747dbe1805f0a6ae68855dccb03dd0f13
Tx public key: 9d49ecc88784622ca0eb35aa799abd47aaa4db40f846a8c95adf74b2035d07b6
Timestamp: 1657093855 Timestamp [UCT]: 2022-07-06 07:50:55 Age [y:d:h:m:s]: 02:184:18:13:50
Block: 537735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 653409 RingCT/type: yes/0
Extra: 019d49ecc88784622ca0eb35aa799abd47aaa4db40f846a8c95adf74b2035d07b60211000000154da16a3a000000000000000000

1 output(s) for total of 10.145206022000 dcy

stealth address amount amount idx
00: 64bd542963b71aed6e3c3f75906da6576460628e65114de1a9e6ec4c85d94c43 10.145206022000 967648 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": 537745, "vin": [ { "gen": { "height": 537735 } } ], "vout": [ { "amount": 10145206022, "target": { "key": "64bd542963b71aed6e3c3f75906da6576460628e65114de1a9e6ec4c85d94c43" } } ], "extra": [ 1, 157, 73, 236, 200, 135, 132, 98, 44, 160, 235, 53, 170, 121, 154, 189, 71, 170, 164, 219, 64, 248, 70, 168, 201, 90, 223, 116, 178, 3, 93, 7, 182, 2, 17, 0, 0, 0, 21, 77, 161, 106, 58, 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