← previous blocknext block →recent activity
Analyzing
Block #90,441,568
8 transactions · 6 stateful · 2026-07-26 08:47:21 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,441,568 · 8 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
2w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c390858…b1ed
0x34b655…2a6f
4 touches
1 conflict
0xa736371d…dcc1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x41f1e2e5…2edf
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x1cc2362d…1fb1
0x34b655…2a6f
2 touches
0 conflicts
0x2bd4c467…ae85
0x34b655…2a6f
2 touches
0 conflicts
0x376c9634…97d2
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 0x2c3908588c…50b1ed
Audit this contract →
← previous block·next block →recent activity