← previous blocknext block →recent activity
Analyzing
Block #106,198,551
25 transactions · 22 stateful · 2026-09-19 14:16:17 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
1.36
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,198,551 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w211w314w015w116w218w420w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7495452f…f803
0x34b655…2a6f
16 touches
28 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x000bde1a…e123
0x34b655…2a6f
6 touches
3 conflicts
0x4abfb389…18f4
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x23a320fb…cbd7
0x34b655…2a6f
4 touches
1 conflict
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 0x7495452f4e…62f803
Audit this contract →
← previous block·next block →recent activity