Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c197ebf96ddc82cd1c693a0b42dbd60cb6ff00dbaa8d6edf21d91262474ed816

Tx prefix hash: 824693d442e367159a645d3242e6e001067b411ae5eb15f63037417b852716a4
Tx public key: 0d6c1b1030ebf55b5cc9bc7aa7350aac91cc40b02a6f1989760df180f647d39f
Timestamp: 1727486684 Timestamp [UCT]: 2024-09-28 01:24:44 Age [y:d:h:m:s]: 00:116:17:47:03
Block: 1119625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83424 RingCT/type: yes/0
Extra: 010d6c1b1030ebf55b5cc9bc7aa7350aac91cc40b02a6f1989760df180f647d39f02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d92c704cb0008bd101b13d14f7fe81150ed30f932c17a54348358cddfe7d5ff0 0.600000000000 1601252 of 15

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": 1119635, "vin": [ { "gen": { "height": 1119625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d92c704cb0008bd101b13d14f7fe81150ed30f932c17a54348358cddfe7d5ff0" } } ], "extra": [ 1, 13, 108, 27, 16, 48, 235, 245, 91, 92, 201, 188, 122, 167, 53, 10, 172, 145, 204, 64, 176, 42, 111, 25, 137, 118, 13, 241, 128, 246, 71, 211, 159, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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