← previous blocknext block →recent activity
Analyzing
Block #106,809,925
25 transactions · 24 stateful · 2026-09-21 17:34:21 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,809,925 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w17w29w010w311w412w515w018w120w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf6b3ac1…433c
0x34b655…2a6f
12 touches
15 conflicts
0x24b2ba87…21ff
0x34b655…2a6f
8 touches
6 conflicts
0x981935b7…709d
0x34b655…2a6f
8 touches
6 conflicts
0x932a9590…0b19
0x34b655…2a6f
8 touches
6 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x5cf2d0c9…0181
0x34b655…2a6f
6 touches
3 conflicts
0x25957369…c648
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xdf6b3ac10c…b0433c
Audit this contract →
← previous block·next block →recent activity