← previous blocknext block →recent activity
Analyzing
Block #105,608,407
10 transactions · 10 stateful · 2026-09-17 12:43:39 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,608,407 · 10 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
1w05w16w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71fad9ce…c11f
0x34b655…2a6f
4 touches
1 conflict
0xa7ecbbe7…f713
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0705cc6c…2c40
0x851145…3f07
4 touches
1 conflict
0xea5af341…ad06
0x851145…3f07
4 touches
1 conflict
0x08d53462…97ef
0x34ae4d…3fc5
2 touches
0 conflicts
0x3a3e7727…36c5
0x34ae4d…3fc5
2 touches
0 conflicts
0x5a409e7f…09b6
0x34ae4d…3fc5
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 0x71fad9ce4b…8ac11f
Audit this contract →
← previous block·next block →recent activity