← previous blocknext block →recent activity
Analyzing
Block #106,234,817
23 transactions · 21 stateful · 2026-09-19 17:18:54 UTC
Parallelism
65/100
Blocked
57%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,234,817 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w28w39w410w512w314w316w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x163c8eca…7b49
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1b5
0x37db7f…ec7b
8 touches
6 conflicts
0x8a35acfb…d1b4
0x37db7f…ec7b
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x0231133a…b339
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity