← previous blocknext block →recent activity
Analyzing
Block #108,918,499
28 transactions · 22 stateful · 2026-09-29 02:33:28 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,918,499 · 28 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
1w02w13w011w115w019w221w122w324w125w026w127w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3347cbe5…846c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x826c0d98…b92f
0x34b655…2a6f
6 touches
3 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
4 touches
1 conflict
0x1f27d6ba…892e
0x34b655…2a6f
4 touches
1 conflict
0x31d9dff4…12bb
0x34b655…2a6f
4 touches
1 conflict
0x342fe47d…42ae
0x34b655…2a6f
4 touches
1 conflict
0x63435b04…27de
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 0x3347cbe5ae…92846c
Audit this contract →
← previous block·next block →recent activity