← previous blocknext block →recent activity
Analyzing
Block #106,431,352
10 transactions · 10 stateful · 2026-09-20 09:47:58 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,431,352 · 10 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0xe5f1ecce…2482
0x34b655…2a6f
4 touches
1 conflict
0x7462b8f2…6312
0x34b655…2a6f
4 touches
1 conflict
0x92b49f44…ee4f
0x34b655…2a6f
4 touches
1 conflict
0x809f2ba8…89d3
0x34b655…2a6f
4 touches
1 conflict
0x2d071de0…c86e
0x34b655…2a6f
2 touches
0 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
2 touches
0 conflicts
0x5bfab785…f2b5
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 0x1b25f26097…52c429
Audit this contract →
← previous block·next block →recent activity