← previous blocknext block →recent activity
Analyzing
Block #90,027,360
12 transactions · 11 stateful · 2026-07-24 21:44:07 UTC
Parallelism
67/100
Blocked
55%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,027,360 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w08w19w310w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8b8fbde…396d
0x34b655…2a6f
4 touches
1 conflict
0xa9614018…d6b4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0e3b59e9…d9d0
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x45ea7a97…bbb3
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 0xa8b8fbdeaa…29396d
Audit this contract →
← previous block·next block →recent activity