← previous blocknext block →recent activity
Analyzing
Block #105,636,866
25 transactions · 22 stateful · 2026-09-17 15:06:56 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,636,866 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w09w114w116w117w218w319w422w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x14046d6a…bc5e
0x34b655…2a6f
10 touches
10 conflicts
0x941bd594…21fd
0x34b655…2a6f
8 touches
6 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
6 touches
3 conflicts
0x3d13406e…eff1
0x34b655…2a6f
6 touches
3 conflicts
0x4ab70ccd…2683
0x34b655…2a6f
6 touches
3 conflicts
0x4dffc33e…068d
0x34b655…2a6f
6 touches
3 conflicts
0xe8f860c0…35c9
0x34b655…2a6f
6 touches
3 conflicts
0x2711a339…af76
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x14046d6aa7…6cbc5e
Audit this contract →
← previous block·next block →recent activity