Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58bf685093b56b58ddc728833010d19606d55ea97dd0cf638e26dac3b79f451e

Tx prefix hash: edd16eb5f939a9f9154d9404f5963d6281f6232a83c1c2a9b816e4e953432403
Tx public key: b4ff0a3ecca099829003d629a3d94ea3a42632588ef543d7abf4f7f57ff270ce
Timestamp: 1716851602 Timestamp [UCT]: 2024-05-27 23:13:22 Age [y:d:h:m:s]: 00:229:01:31:09
Block: 1031460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163928 RingCT/type: yes/0
Extra: 01b4ff0a3ecca099829003d629a3d94ea3a42632588ef543d7abf4f7f57ff270ce0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c92656b481e6ec9b89f8188b2cf639fdd6477a758e36d342239ee5de141419a9 0.600000000000 1499907 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": 1031470, "vin": [ { "gen": { "height": 1031460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c92656b481e6ec9b89f8188b2cf639fdd6477a758e36d342239ee5de141419a9" } } ], "extra": [ 1, 180, 255, 10, 62, 204, 160, 153, 130, 144, 3, 214, 41, 163, 217, 78, 163, 164, 38, 50, 88, 142, 245, 67, 215, 171, 244, 247, 245, 127, 242, 112, 206, 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