← previous blocknext block →recent activity
Analyzing
Block #105,932,921
17 transactions · 16 stateful · 2026-09-18 15:59:17 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,932,921 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w06w18w110w111w012w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d5d1fb5…86a7
0x34b655…2a6f
6 touches
3 conflicts
0x12e605da…9ca3
0x34b655…2a6f
4 touches
1 conflict
0x12e77486…ec2b
0x34b655…2a6f
4 touches
1 conflict
0x184e765d…08f6
0x34b655…2a6f
4 touches
1 conflict
0x309f47c0…e1cf
0x34b655…2a6f
4 touches
1 conflict
0x3b65c5ca…9f83
0x34b655…2a6f
4 touches
1 conflict
0x3c9b10c1…d791
0x34b655…2a6f
4 touches
1 conflict
0x55cde02d…89cb
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
3 conflicts on slot 0x6d5d1fb525…a986a7
Audit this contract →
← previous block·next block →recent activity