← previous blocknext block →recent activity
Analyzing
Block #106,215,587
31 transactions · 29 stateful · 2026-09-19 15:42:05 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,215,587 · 31 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
1w02w05w06w07w18w19w211w312w413w515w622w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc737ce4f…a8d8
0x34b655…2a6f
12 touches
15 conflicts
0xbf0dd721…6823
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xd2d5c309…882d
0x34b655…2a6f
6 touches
3 conflicts
0xd3b84582…0ade
0x34b655…2a6f
6 touches
3 conflicts
0xab981df1…2941
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
15 conflicts on slot 0xc737ce4f46…1fa8d8
Audit this contract →
← previous block·next block →recent activity