← previous blocknext block →recent activity
Analyzing
Block #105,625,891
28 transactions · 26 stateful · 2026-09-17 14:11:41 UTC
Parallelism
89/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,625,891 · 28 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
1w03w04w15w012w113w118w119w221w122w026w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf537d3a9…730b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x1a79e9de…99e6
0x851145…3f07
4 touches
1 conflict
0xc73fd549…2e28
0x851145…3f07
4 touches
1 conflict
0xd840c9df…2d85
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
1 conflict on slot 0xf537d3a965…67730b
Audit this contract →
← previous block·next block →recent activity