← previous blocknext block →recent activity
Analyzing
Block #106,357,299
28 transactions · 24 stateful · 2026-09-20 03:35:17 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.82
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,357,299 · 28 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
1w02w13w14w05w16w27w39w310w415w420w422w525w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe890a5b…ac60
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x25bd380f…a658
0x34b655…2a6f
6 touches
3 conflicts
0x8765edd1…a7d5
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
10 conflicts on slot 0xfe890a5b12…49ac60
Audit this contract →
← previous block·next block →recent activity