← previous blocknext block →recent activity
Analyzing
Block #106,235,418
12 transactions · 12 stateful · 2026-09-19 17:21:56 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,235,418 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd52c81a0…1885
0x34b655…2a6f
4 touches
1 conflict
0xe7826b5b…166a
0x34b655…2a6f
4 touches
1 conflict
0x6d426cdf…360d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x6d426cdf…360c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xbfca3cd0…5023
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xd52c81a04c…c31885
Audit this contract →
← previous block·next block →recent activity