← previous blocknext block →recent activity
Analyzing
Block #90,558,587
7 transactions · 6 stateful · 2026-07-26 18:36:17 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,558,587 · 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
1w02w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64a785e4…0110
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x00becc92…0d23
0x34b655…2a6f
2 touches
0 conflicts
0x0d336deb…3fee
0x34b655…2a6f
2 touches
0 conflicts
0x0db691ab…3ee3
0x34b655…2a6f
2 touches
0 conflicts
0x1adc270e…f7f6
0x34b655…2a6f
2 touches
0 conflicts
0x238aa6a0…f7d2
0x34b655…2a6f
2 touches
0 conflicts
0x28ad10b2…8b95
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 0x64a785e491…1c0110
Audit this contract →
← previous block·next block →recent activity