← previous blocknext block →recent activity
Analyzing
Block #90,439,955
8 transactions · 7 stateful · 2026-07-26 08:39:08 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,439,955 · 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
2w03w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x8a4ab7ad…876a
0x34b655…2a6f
4 touches
1 conflict
0x33dde6d3…c08b
0x34b655…2a6f
4 touches
1 conflict
0xe75060c3…b41e
0x34b655…2a6f
4 touches
1 conflict
0x60c4435a…22ca
0x34b655…2a6f
2 touches
0 conflicts
0x60c4435a…22cb
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
3 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity