← previous blocknext block →recent activity
Analyzing
Block #90,395,882
12 transactions · 11 stateful · 2026-07-26 04:52:38 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,395,882 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x826cce18…251c
0x34b655…2a6f
4 touches
1 conflict
0x9fa5be00…fb16
0x34b655…2a6f
4 touches
1 conflict
0xb3f008b3…b7c9
0x34b655…2a6f
4 touches
1 conflict
0xf85bdc12…5dff
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0abf7b77…0d80
0x34b655…2a6f
4 touches
1 conflict
0x37c70870…b872
0x34b655…2a6f
4 touches
1 conflict
0x4c188934…158e
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
1 conflict on slot 0x826cce18ca…e5251c
Audit this contract →
← previous block·next block →recent activity