← previous blocknext block →recent activity
Analyzing
Block #106,207,763
31 transactions · 26 stateful · 2026-09-19 15:02:42 UTC
Parallelism
87/100
Blocked
46%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,207,763 · 31 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
2w04w05w16w07w18w210w017w318w119w020w123w225w126w227w329w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x800bbaf8…b709
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x238fcad4…5907
0x34b655…2a6f
4 touches
1 conflict
0x3a144c87…82db
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
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
6 conflicts on slot 0x800bbaf8ad…d8b709
Audit this contract →
← previous block·next block →recent activity