← previous blocknext block →recent activity
Analyzing
Block #93,137,562
13 transactions · 13 stateful · 2026-08-04 18:55:17 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,137,562 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w08w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd75651f…c1f3
0x34b655…2a6f
6 touches
3 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
6 touches
3 conflicts
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x11db128b…1153
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x6bab0076…422b
0x34b655…2a6f
4 touches
1 conflict
0x7ec9cda3…6ddb
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
3 conflicts on slot 0xfd75651f18…a5c1f3
Audit this contract →
← previous block·next block →recent activity