← previous blocknext block →recent activity
Analyzing
Block #106,434,136
18 transactions · 18 stateful · 2026-09-20 10:01:59 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,434,136 · 18 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
1w02w13w26w17w28w39w415w016w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
10 touches
10 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0xeddb6c44…d47e
0x34b655…2a6f
10 touches
10 conflicts
0x5f76b8ee…ecfe
0x34b655…2a6f
8 touches
6 conflicts
0x74cdc294…26a8
0x34b655…2a6f
8 touches
6 conflicts
0x9d6a99f9…da64
0x34b655…2a6f
8 touches
6 conflicts
0xa7f7a563…4504
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity