Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0837e4bba973b0c3b4db80e6deb11388e643de219fd3c3bd07a6eeecc90eb60c

Tx prefix hash: 337daf2ccb53893bacea66d6f9301275447a9775a9eda6c9c4e199e3f51abb2f
Tx public key: 16acb53ad3b5f955123152e14e3ed12b584ae227c83a1d085f7a2eea975ecce2
Timestamp: 1704921237 Timestamp [UCT]: 2024-01-10 21:13:57 Age [y:d:h:m:s]: 01:081:01:48:07
Block: 932526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319050 RingCT/type: yes/0
Extra: 0116acb53ad3b5f955123152e14e3ed12b584ae227c83a1d085f7a2eea975ecce20211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efdab356aa3b39b5434bbe36e9ca0edc60f875d02aefae54d88579ed2bf45d01 0.600000000000 1390462 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": 932536, "vin": [ { "gen": { "height": 932526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efdab356aa3b39b5434bbe36e9ca0edc60f875d02aefae54d88579ed2bf45d01" } } ], "extra": [ 1, 22, 172, 181, 58, 211, 181, 249, 85, 18, 49, 82, 225, 78, 62, 209, 43, 88, 74, 226, 39, 200, 58, 29, 8, 95, 122, 46, 234, 151, 94, 204, 226, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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