Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 795a19831474d5b70b0732d16a8e71392c8a5e964bbeec38a50c8931a790b385

Tx prefix hash: 58ecdd7d7c6f985e77af3fb49cbdfae641b634c9a216e7dccc185ecafc56d5aa
Tx public key: 57e15f7b9fe16c0ee211fac82136a2a38cf1fb557f64699cb9ab0b0deb671199
Timestamp: 1713759108 Timestamp [UCT]: 2024-04-22 04:11:48 Age [y:d:h:m:s]: 00:207:08:39:16
Block: 1005810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148443 RingCT/type: yes/0
Extra: 0157e15f7b9fe16c0ee211fac82136a2a38cf1fb557f64699cb9ab0b0deb6711990211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce5c940f52cf2747770c0984d96f5073f2d94eac81a100cfdf5b6c2b81df3f70 0.600000000000 1466620 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": 1005820, "vin": [ { "gen": { "height": 1005810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce5c940f52cf2747770c0984d96f5073f2d94eac81a100cfdf5b6c2b81df3f70" } } ], "extra": [ 1, 87, 225, 95, 123, 159, 225, 108, 14, 226, 17, 250, 200, 33, 54, 162, 163, 140, 241, 251, 85, 127, 100, 105, 156, 185, 171, 11, 13, 235, 103, 17, 153, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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