Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d3b2ea6b82dbdc800c9878c6f9e48b0b4cf49e0eb0a87ec1a682bd1e04e132a

Tx prefix hash: 5e8266c845a5c3ff292909b936f16561e1ca927dfe2de86706132844df90b138
Tx public key: 77a04fc82cf9863bd9a1b2c454027ce7136ec623edcf5bc93d076e59a5dad2db
Timestamp: 1708301873 Timestamp [UCT]: 2024-02-19 00:17:53 Age [y:d:h:m:s]: 01:045:23:00:30
Block: 960568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293876 RingCT/type: yes/0
Extra: 0177a04fc82cf9863bd9a1b2c454027ce7136ec623edcf5bc93d076e59a5dad2db0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cb362af0cda30dea009d52ca60034c7cdf6143d99a6f5134745dfe68ba520c9 0.600000000000 1420139 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": 960578, "vin": [ { "gen": { "height": 960568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cb362af0cda30dea009d52ca60034c7cdf6143d99a6f5134745dfe68ba520c9" } } ], "extra": [ 1, 119, 160, 79, 200, 44, 249, 134, 59, 217, 161, 178, 196, 84, 2, 124, 231, 19, 110, 198, 35, 237, 207, 91, 201, 61, 7, 110, 89, 165, 218, 210, 219, 2, 17, 0, 0, 0, 6, 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