← previous blocknext block →recent activity
Analyzing
Block #106,155,216
26 transactions · 22 stateful · 2026-09-19 10:38:12 UTC
Parallelism
73/100
Blocked
64%
Avg conflicts / tx
1.73
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,155,216 · 26 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
1w02w13w04w15w16w27w08w29w312w213w315w317w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x976029c0…a4de
0x34b655…2a6f
10 touches
10 conflicts
0xd41f5136…97c6
0x34b655…2a6f
10 touches
10 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x719e7a70…cd01
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xfe39a1f7…8eb0
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
10 conflicts on slot 0x976029c05b…f4a4de
Audit this contract →
← previous block·next block →recent activity