Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f576840b3e2501cd6e0f9b8ec8e5bf0977f04ab74f66d11c82279aa929a7c0f9

Tx prefix hash: 8b391017ad1d70d35943543a869706cb00d658f44932c371c6c473545dcc206b
Tx public key: bcefc5e93d2ef501c79338f17d1dfdf0ab93d1a591565fb7ece4b97ab16e901d
Timestamp: 1706464877 Timestamp [UCT]: 2024-01-28 18:01:17 Age [y:d:h:m:s]: 01:071:00:32:24
Block: 945321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311837 RingCT/type: yes/0
Extra: 01bcefc5e93d2ef501c79338f17d1dfdf0ab93d1a591565fb7ece4b97ab16e901d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f131887093ccb26900b9058749beb039deda28cc6024e7730e918772b676c5e 0.600000000000 1403633 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": 945331, "vin": [ { "gen": { "height": 945321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f131887093ccb26900b9058749beb039deda28cc6024e7730e918772b676c5e" } } ], "extra": [ 1, 188, 239, 197, 233, 61, 46, 245, 1, 199, 147, 56, 241, 125, 29, 253, 240, 171, 147, 209, 165, 145, 86, 95, 183, 236, 228, 185, 122, 177, 110, 144, 29, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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