← previous blocknext block →recent activity
Analyzing
Block #90,328,896
11 transactions · 10 stateful · 2026-07-25 23:09:09 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,328,896 · 11 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
1w02w14w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde1fb60f…e5c5
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xb245fe36…d765
0x34b655…2a6f
4 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
2 touches
0 conflicts
0x033cf007…136d
0x34b655…2a6f
2 touches
0 conflicts
0x4abd2e60…8398
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 0xde1fb60fae…ebe5c5
Audit this contract →
← previous block·next block →recent activity