← previous blocknext block →recent activity
Analyzing
Block #93,322,217
17 transactions · 15 stateful · 2026-08-05 10:23:46 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,322,217 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xae085366…fa10
0x34b655…2a6f
6 touches
3 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
4 touches
1 conflict
0x242fd968…26ed
0x34b655…2a6f
4 touches
1 conflict
0x242fd968…26ee
0x34b655…2a6f
4 touches
1 conflict
0x6a2521fa…2320
0x34b655…2a6f
4 touches
1 conflict
0x9c79b492…a68c
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity