Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e94ebbf4c4640062a9d8e0ef35622dcb703526e0e79eecbafe808940b64077c3

Tx prefix hash: b8f6afb65dac5319021786456adea222fcd3f3b4d853e182c7544256f76e312e
Tx public key: cb61e3421b2f616813e3817fe6ef1cc649ff38b4eee58103d38eec7a26e2b41e
Timestamp: 1720843033 Timestamp [UCT]: 2024-07-13 03:57:13 Age [y:d:h:m:s]: 00:245:10:58:10
Block: 1064555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175361 RingCT/type: yes/0
Extra: 01cb61e3421b2f616813e3817fe6ef1cc649ff38b4eee58103d38eec7a26e2b41e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4583e50ce47ce4f922afa8d97cb54bf157d99a62c5e895b0bdc1c67a1e1b1669 0.600000000000 1535084 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": 1064565, "vin": [ { "gen": { "height": 1064555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4583e50ce47ce4f922afa8d97cb54bf157d99a62c5e895b0bdc1c67a1e1b1669" } } ], "extra": [ 1, 203, 97, 227, 66, 27, 47, 97, 104, 19, 227, 129, 127, 230, 239, 28, 198, 73, 255, 56, 180, 238, 229, 129, 3, 211, 142, 236, 122, 38, 226, 180, 30, 2, 17, 0, 0, 0, 1, 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