← previous blocknext block →recent activity
Analyzing
Block #90,205,299
7 transactions · 6 stateful · 2026-07-25 12:43:53 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,205,299 · 7 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x069e7e09…ff8a
0x34b655…2a6f
2 touches
0 conflicts
0x108d1213…e37d
0x34b655…2a6f
2 touches
0 conflicts
0x12378f48…40bb
0x34b655…2a6f
2 touches
0 conflicts
0x19a49e01…677c
0x34b655…2a6f
2 touches
0 conflicts
0x1a3cabd4…f0a9
0x34b655…2a6f
2 touches
0 conflicts
0x1c3295fd…097a
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity