← previous blocknext block →recent activity
Analyzing
Block #105,402,336
35 transactions · 29 stateful · 2026-09-16 19:26:31 UTC
Parallelism
91/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,402,336 · 35 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w06w07w19w011w114w015w116w220w022w127w128w132w234w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x020ad0d8…8110
0x34b655…2a6f
6 touches
3 conflicts
0xed252c0a…b47e
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb86
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x49890ced…6f23
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
3 conflicts on slot 0x020ad0d832…fb8110
Audit this contract →
← previous block·next block →recent activity