← previous blocknext block →recent activity
Analyzing
Block #93,363,754
24 transactions · 22 stateful · 2026-08-05 13:52:36 UTC
Parallelism
71/100
Blocked
68%
Avg conflicts / tx
1.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,363,754 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w27w38w29w310w416w417w118w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8bc53a3…c2fe
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd39bcac4…fcff
0x34b655…2a6f
6 touches
3 conflicts
0x77f5ee28…347d
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
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
21 conflicts on slot 0xd8bc53a346…42c2fe
Audit this contract →
← previous block·next block →recent activity