← previous blocknext block →recent activity
Analyzing
Block #105,538,807
12 transactions · 12 stateful · 2026-09-17 06:53:19 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,538,807 · 12 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
5w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
0xfd4e632c…e14c
0x34b655…2a6f
4 touches
1 conflict
0xb08ad59f…c4fb
0x34b655…2a6f
4 touches
1 conflict
0xdac7e046…6ea7
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x617c91fa…b452
0x34b655…2a6f
2 touches
0 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
2 touches
0 conflicts
0x941bd594…21fd
0x34b655…2a6f
2 touches
0 conflicts
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 0x502b3ee1e6…227f7c
Audit this contract →
← previous block·next block →recent activity