← previous blocknext block →recent activity
Analyzing
Block #93,315,548
11 transactions · 9 stateful · 2026-08-05 09:50:14 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,315,548 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bea6eae…9f7b
0x34b655…2a6f
4 touches
1 conflict
0x2b64d0d7…af06
0x34b655…2a6f
4 touches
1 conflict
0x7f63a266…68c0
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0c970d6e…72c6
0x34b655…2a6f
2 touches
0 conflicts
0x0cc65720…396c
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x2bea6eae34…b89f7b
Audit this contract →
← previous block·next block →recent activity