← previous blocknext block →recent activity
Analyzing
Block #105,410,884
16 transactions · 16 stateful · 2026-09-16 20:09:34 UTC
Parallelism
63/100
Blocked
31%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,410,884 · 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
2w04w15w210w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2557abf8…2901
0x34b655…2a6f
10 touches
10 conflicts
0xde0b0123…40ac
0x34b655…2a6f
10 touches
10 conflicts
0xee8237bd…46ad
0x34b655…2a6f
6 touches
3 conflicts
0x2378c6e1…4dbd
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x9f2bf688…a44f
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
10 conflicts on slot 0x2557abf8e3…0a2901
Audit this contract →
← previous block·next block →recent activity