← previous blocknext block →recent activity
Analyzing
Block #106,931,376
23 transactions · 22 stateful · 2026-09-22 03:45:40 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,931,376 · 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
5w06w17w28w39w010w111w412w013w214w315w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x715eeec8…5664
0x34b655…2a6f
14 touches
21 conflicts
0xa9988419…9f45
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
10 touches
10 conflicts
0xcaeee6b1…56a0
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
6 touches
3 conflicts
0xb4a968cb…e2fa
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
21 conflicts on slot 0x715eeec877…cd5664
Audit this contract →
← previous block·next block →recent activity