← previous blocknext block →recent activity
Analyzing
Block #106,934,009
13 transactions · 13 stateful · 2026-09-22 03:58:54 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,934,009 · 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
5w06w07w18w29w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388ab72e…e6e6
0x34b655…2a6f
8 touches
6 conflicts
0x7462b8f2…6312
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0x4ea9cee5…bf74
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
0x29a58269…011a
0x34b655…2a6f
2 touches
0 conflicts
0x32e20e7f…6994
0x34b655…2a6f
2 touches
0 conflicts
0x33b7fbba…64de
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
6 conflicts on slot 0x388ab72e91…70e6e6
Audit this contract →
← previous block·next block →recent activity