Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f090ef3d9449c0a93218b9771910e77f866475c6462c34b2838d34bceb428235

Tx prefix hash: b790b263b2b22142c9e3cbc6623429cce0457d89871cae619d08e7599b820bc8
Tx public key: 1fa58df4f0c9fe1669ee82c97a02c281e1aa90cd7bfeb0aefd81a19ee25fe656
Timestamp: 1727531179 Timestamp [UCT]: 2024-09-28 13:46:19 Age [y:d:h:m:s]: 00:212:02:01:26
Block: 1120003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151401 RingCT/type: yes/0
Extra: 011fa58df4f0c9fe1669ee82c97a02c281e1aa90cd7bfeb0aefd81a19ee25fe65602110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ce6b8735e2a1d776a8f7ff4fbdae4e860939756bafccbce2b86499284f68faa 0.600000000000 1601764 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": 1120013, "vin": [ { "gen": { "height": 1120003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ce6b8735e2a1d776a8f7ff4fbdae4e860939756bafccbce2b86499284f68faa" } } ], "extra": [ 1, 31, 165, 141, 244, 240, 201, 254, 22, 105, 238, 130, 201, 122, 2, 194, 129, 225, 170, 144, 205, 123, 254, 176, 174, 253, 129, 161, 158, 226, 95, 230, 86, 2, 17, 0, 0, 0, 9, 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