← previous blocknext block →recent activity
Analyzing
Block #105,920,419
22 transactions · 22 stateful · 2026-09-18 14:56:21 UTC
Parallelism
82/100
Blocked
36%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,920,419 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w29w310w112w015w016w117w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
6 touches
3 conflicts
0xaf59c69d…c904
0x37db7f…ec7b
6 touches
3 conflicts
0xf99548c6…30b3
0x37db7f…ec7b
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x24c5620c…7ac5
0x34b655…2a6f
6 touches
3 conflicts
0x3d6c26e5…1b45
0x34b655…2a6f
6 touches
3 conflicts
0x5d0915af…762d
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity