← previous blocknext block →recent activity
Analyzing
Block #106,234,810
38 transactions · 30 stateful · 2026-09-19 17:18:52 UTC
Parallelism
84/100
Blocked
57%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,234,810 · 38 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
2w03w04w110w011w012w013w117w020w221w322w423w124w126w427w535w137w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x163c8eca…7b49
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x08ea9a75…bfc5
0x34b655…2a6f
10 touches
10 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
6 touches
3 conflicts
0xcda3e7fd…3055
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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 0x163c8eca47…047b49
Audit this contract →
← previous block·next block →recent activity