← previous blocknext block →recent activity
Analyzing
Block #106,235,343
33 transactions · 31 stateful · 2026-09-19 17:21:33 UTC
Parallelism
76/100
Blocked
71%
Avg conflicts / tx
1.94
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,235,343 · 33 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w18w39w310w416w217w520w122w223w324w425w526w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf00e711b…c539
0x34b655…2a6f
16 touches
28 conflicts
0xde1dc398…c78f
0x34b655…2a6f
14 touches
21 conflicts
0x30ae635d…5e67
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xb550abea…2729
0x34b655…2a6f
10 touches
10 conflicts
0x6fc86638…74ed
0x34b655…2a6f
10 touches
10 conflicts
0xc61ecf05…2972
0xa6afd3…d132
6 touches
3 conflicts
0x61ace914…07b5
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
28 conflicts on slot 0xf00e711b37…00c539
Audit this contract →
← previous block·next block →recent activity