← previous blocknext block →recent activity
Analyzing
Block #90,536,460
21 transactions · 18 stateful · 2026-07-26 16:44:59 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,536,460 · 21 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
1w02w18w09w110w111w212w115w317w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7c1aa35…e064
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x1565183a…e0a0
0x34b655…2a6f
4 touches
1 conflict
0x200444bb…b23b
0x34b655…2a6f
4 touches
1 conflict
0x45d3434f…6c0c
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
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 0xe7c1aa35d1…b8e064
Audit this contract →
← previous block·next block →recent activity