← previous blocknext block →recent activity
Analyzing
Block #90,976,105
16 transactions · 16 stateful · 2026-07-28 05:36:48 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,976,105 · 16 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
2w03w14w25w06w17w18w214w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8435cea0…f5b6
0x34b655…2a6f
6 touches
3 conflicts
0x6e6b8ec7…2197
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x72083f0d…082a
0x34b655…2a6f
4 touches
1 conflict
0x83dee4ed…fbad
0x34b655…2a6f
4 touches
1 conflict
0x9b2511ba…3812
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 0x8435cea01a…60f5b6
Audit this contract →
← previous block·next block →recent activity