Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8403ea1f531a4e0ad53b78f8ffba21cf6a124e8c20321dbe8a817b4642d40929

Tx prefix hash: 237aa766ebe306577e53ae3caaa1eff6d8c7054fa90f4a95dbb35a260dcf5d11
Tx public key: 7068d57cf4ca0a4b4ff906ffa6284934ba265463d79c7bd2aeeed145930e3fdd
Timestamp: 1722117028 Timestamp [UCT]: 2024-07-27 21:50:28 Age [y:d:h:m:s]: 00:288:16:02:51
Block: 1075108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206240 RingCT/type: yes/0
Extra: 017068d57cf4ca0a4b4ff906ffa6284934ba265463d79c7bd2aeeed145930e3fdd02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89486d9bcb18257c83a52aa048a7d77feb60f1cbc9ef50c74e9df7e8263bce0e 0.600000000000 1547631 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": 1075118, "vin": [ { "gen": { "height": 1075108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89486d9bcb18257c83a52aa048a7d77feb60f1cbc9ef50c74e9df7e8263bce0e" } } ], "extra": [ 1, 112, 104, 213, 124, 244, 202, 10, 75, 79, 249, 6, 255, 166, 40, 73, 52, 186, 38, 84, 99, 215, 156, 123, 210, 174, 238, 209, 69, 147, 14, 63, 221, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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