← previous blocknext block →recent activity
Analyzing
Block #106,551,417
24 transactions · 24 stateful · 2026-09-20 19:52:17 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,551,417 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w06w112w213w314w315w416w121w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54f7f60f…43cc
0x34b655…2a6f
8 touches
6 conflicts
0xf9baf24c…c1fe
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
8 touches
6 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xbc1888a9…2a59
0x34b655…2a6f
8 touches
6 conflicts
0x07c47b1c…93c8
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
6 conflicts on slot 0x54f7f60f23…cb43cc
Audit this contract →
← previous block·next block →recent activity