← previous blocknext block →recent activity
Analyzing
Block #106,534,312
20 transactions · 20 stateful · 2026-09-20 18:26:12 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,534,312 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w29w210w111w112w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd41f5136…97c6
0x34b655…2a6f
14 touches
21 conflicts
0x684d04c0…37c4
0x34b655…2a6f
10 touches
10 conflicts
0x86cea35b…bdff
0x34b655…2a6f
8 touches
6 conflicts
0xf788c790…e66f
0x34b655…2a6f
8 touches
6 conflicts
0x549c41f3…3e6c
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x8a1c9e92…67b0
0x34b655…2a6f
6 touches
3 conflicts
0x4293dc18…310b
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
21 conflicts on slot 0xd41f513688…4197c6
Audit this contract →
← previous block·next block →recent activity