← previous blocknext block →recent activity
Analyzing
Block #90,814,940
29 transactions · 22 stateful · 2026-07-27 16:06:02 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,814,940 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w112w013w114w216w117w118w119w020w225w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41377979…0a18
0x34b655…2a6f
8 touches
6 conflicts
0x0bd95eb4…e562
0x34b655…2a6f
6 touches
3 conflicts
0xa3f6f7c8…2436
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x6a02247d…f9ed
0x34b655…2a6f
4 touches
1 conflict
0x8861b270…e0cb
0x34b655…2a6f
4 touches
1 conflict
0x9fec3c31…4ec6
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
6 conflicts on slot 0x413779793d…8f0a18
Audit this contract →
← previous block·next block →recent activity