← previous blocknext block →recent activity
Analyzing
Block #90,439,600
7 transactions · 5 stateful · 2026-07-26 08:37:20 UTC
Parallelism
57/100
Blocked
40%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,439,600 · 7 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
2w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d7e3f62…e2cc
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0c300593…1bf9
0x34b655…2a6f
2 touches
0 conflicts
0x16e75abd…f3ad
0x34b655…2a6f
2 touches
0 conflicts
0x70b7b52e…7743
0x34b655…2a6f
2 touches
0 conflicts
0x70b7b52e…7744
0x34b655…2a6f
2 touches
0 conflicts
0x9ddc4efa…8e27
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 0x8d7e3f6296…16e2cc
Audit this contract →
← previous block·next block →recent activity