Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1112281b9026ce2dc76ca758885d76cd97907e99568dcdc7e19d8bf2aaee27ee

Tx prefix hash: 354cd9c0bba86f0aec7cefa72b474967fb66e137f9f8558f1abc758a2dd8accf
Tx public key: eb6cd0fb1286927cb304c4912ac0eaec0663e6f8f4d90f4db225cf655d40190f
Timestamp: 1702686360 Timestamp [UCT]: 2023-12-16 00:26:00 Age [y:d:h:m:s]: 01:035:17:15:49
Block: 914008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286864 RingCT/type: yes/0
Extra: 01eb6cd0fb1286927cb304c4912ac0eaec0663e6f8f4d90f4db225cf655d40190f02110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4526a2dd8bb0ec7c9a7c3997fa5a23e61ddc71a72e81dd64ae09a4fe581b5f1e 0.600000000000 1371288 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": 914018, "vin": [ { "gen": { "height": 914008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4526a2dd8bb0ec7c9a7c3997fa5a23e61ddc71a72e81dd64ae09a4fe581b5f1e" } } ], "extra": [ 1, 235, 108, 208, 251, 18, 134, 146, 124, 179, 4, 196, 145, 42, 192, 234, 236, 6, 99, 230, 248, 244, 217, 15, 77, 178, 37, 207, 101, 93, 64, 25, 15, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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