← previous blocknext block →recent activity
Analyzing
Block #106,185,777
25 transactions · 23 stateful · 2026-09-19 13:12:00 UTC
Parallelism
80/100
Blocked
26%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,185,777 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w07w113w119w020w121w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc166a323…1f33
0x34b655…2a6f
4 touches
1 conflict
0xc228863b…2428
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0xb62d7621…0b25
0x34b655…2a6f
4 touches
1 conflict
0x9340e06b…1581
0x34b655…2a6f
4 touches
1 conflict
0xfda729a6…3a4e
0x34b655…2a6f
4 touches
1 conflict
0x17c93766…889e
0x34b655…2a6f
3 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity