← previous blocknext block →recent activity
Analyzing
Block #105,845,162
16 transactions · 16 stateful · 2026-09-18 08:36:41 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,845,162 · 16 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
2w03w04w16w07w18w19w210w311w412w515w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd7f5b55…4994
0x34b655…2a6f
12 touches
15 conflicts
0x6c71e822…1263
0x34b655…2a6f
8 touches
6 conflicts
0x46f78cfd…3f67
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
6 touches
3 conflicts
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
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
15 conflicts on slot 0xfd7f5b557f…f74994
Audit this contract →
← previous block·next block →recent activity