← previous blocknext block →recent activity
Analyzing
Block #106,273,682
17 transactions · 17 stateful · 2026-09-19 20:34:30 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
1.18
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,273,682 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w212w213w314w015w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ae38164…15f0
0x34b655…2a6f
10 touches
10 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
10 touches
10 conflicts
0x784f870c…0bfb
0x34b655…2a6f
10 touches
10 conflicts
0x21e79ad8…c5db
0x34b655…2a6f
8 touches
6 conflicts
0x0203a60f…d0bd
0x34b655…2a6f
8 touches
6 conflicts
0x8b7e5c4e…5fae
0x34b655…2a6f
6 touches
3 conflicts
0x90b49c59…4807
0x34b655…2a6f
6 touches
3 conflicts
0x98dd86bb…1edb
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 0x4ae38164ed…0215f0
Audit this contract →
← previous block·next block →recent activity