← previous blocknext block →recent activity
Analyzing
Block #90,958,363
6 transactions · 6 stateful · 2026-07-28 04:07:32 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,958,363 · 6 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
1w02w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0bdc8f8b…932e
0x34b655…2a6f
2 touches
0 conflicts
0x0e7dbafc…0ac6
0x34b655…2a6f
2 touches
0 conflicts
0x17b720f5…ad7a
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity