← previous blocknext block →recent activity
Analyzing
Block #106,185,954
27 transactions · 24 stateful · 2026-09-19 13:12:54 UTC
Parallelism
74/100
Blocked
42%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,185,954 · 27 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
1w03w04w17w08w09w111w013w115w216w317w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa66bdd0…45f5
0x34b655…2a6f
14 touches
21 conflicts
0xb654bd89…a83b
0x34b655…2a6f
8 touches
6 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
8 touches
6 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
8 touches
6 conflicts
0x2631b5d1…886b
0x34b655…2a6f
6 touches
3 conflicts
0x9375a764…dca1
0x34b655…2a6f
6 touches
3 conflicts
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
21 conflicts on slot 0xfa66bdd005…ea45f5
Audit this contract →
← previous block·next block →recent activity