← previous blocknext block →recent activity
Analyzing
Block #106,917,896
30 transactions · 29 stateful · 2026-09-22 02:37:49 UTC
Parallelism
87/100
Blocked
24%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,917,896 · 30 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
4w09w010w011w113w014w115w216w317w118w019w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb3c5c27…d699
0x34b655…2a6f
8 touches
6 conflicts
0x6a9e408e…3721
0x34b655…2a6f
6 touches
3 conflicts
0x518221db…65f7
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x2877f440…c2c8
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
6 conflicts on slot 0xfb3c5c2775…2bd699
Audit this contract →
← previous block·next block →recent activity