← previous blocknext block →recent activity
Analyzing
Block #105,367,403
16 transactions · 15 stateful · 2026-09-16 16:30:37 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,367,403 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w110w111w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05a81321…6170
0x34b655…2a6f
4 touches
1 conflict
0x05ae4d3e…3c79
0x34b655…2a6f
4 touches
1 conflict
0x0a8f8b9c…3046
0x34b655…2a6f
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x126c10ea…a328
0x34b655…2a6f
4 touches
1 conflict
0x198a44fd…98d2
0x34b655…2a6f
4 touches
1 conflict
0x20577858…5cfd
0x34b655…2a6f
4 touches
1 conflict
0x29569f4d…31e2
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
1 conflict on slot 0x05a81321f8…ba6170
Audit this contract →
← previous block·next block →recent activity