← previous blocknext block →recent activity
Analyzing
Block #105,672,726
17 transactions · 15 stateful · 2026-09-17 18:07:27 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,672,726 · 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
1w02w13w04w15w26w111w212w314w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xeb5b61a2…b2bc
0x34b655…2a6f
6 touches
3 conflicts
0xea5af341…ad06
0x851145…3f07
4 touches
1 conflict
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0x4847c505…b303
0x34b655…2a6f
4 touches
1 conflict
0xdaf02dea…dbd8
0x34b655…2a6f
4 touches
1 conflict
0xf61fea0c…4532
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
6 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity