← previous blocknext block →recent activity
Analyzing
Block #90,207,270
18 transactions · 17 stateful · 2026-07-25 12:53:48 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,207,270 · 18 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
1w02w13w04w15w06w08w29w110w011w113w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe97d00dd…0980
0x34b655…2a6f
4 touches
1 conflict
0x8fa9bc45…e08f
0xa6afd3…d132
4 touches
1 conflict
0x43fab434…896f
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0x159a1084…1341
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
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
1 conflict on slot 0xe97d00dd4b…b80980
Audit this contract →
← previous block·next block →recent activity