Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 202e7ab34c133a246d87041d7286d135731d5973ea9694f5abd59b6aaacd8687

Tx prefix hash: 6be224a1c516605492b2b650f2bfc0ff1be3fb63b7422139f98275a0c08354d0
Tx public key: 8d0109f75d7ae9c3dfce04ac181f21edc56157a23102543cd5bc83b97dbf9bc8
Timestamp: 1716761784 Timestamp [UCT]: 2024-05-26 22:16:24 Age [y:d:h:m:s]: 00:345:08:33:22
Block: 1030719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246842 RingCT/type: yes/0
Extra: 018d0109f75d7ae9c3dfce04ac181f21edc56157a23102543cd5bc83b97dbf9bc80211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b78f23e7a948a10f127fc6e16b2a978b3376d906ec1b75dae052d5601ddc2959 0.600000000000 1498988 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": 1030729, "vin": [ { "gen": { "height": 1030719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b78f23e7a948a10f127fc6e16b2a978b3376d906ec1b75dae052d5601ddc2959" } } ], "extra": [ 1, 141, 1, 9, 247, 93, 122, 233, 195, 223, 206, 4, 172, 24, 31, 33, 237, 197, 97, 87, 162, 49, 2, 84, 60, 213, 188, 131, 185, 125, 191, 155, 200, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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