← previous blocknext block →recent activity
Analyzing
Block #106,187,124
19 transactions · 17 stateful · 2026-09-19 13:18:47 UTC
Parallelism
68/100
Blocked
35%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,187,124 · 19 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
2w04w05w111w112w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e2ddb96…2285
0x34b655…2a6f
12 touches
15 conflicts
0x000bde1a…e123
0x34b655…2a6f
6 touches
3 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
6 touches
3 conflicts
0x76ed8777…1e5f
0x34b655…2a6f
6 touches
3 conflicts
0x35b89cd8…5092
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x0ec5a1b3…54d5
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
15 conflicts on slot 0x7e2ddb965d…af2285
Audit this contract →
← previous block·next block →recent activity