← previous blocknext block →recent activity
Analyzing
Block #90,770,113
13 transactions · 11 stateful · 2026-07-27 12:20:23 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,770,113 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w110w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53ca3f7a…a3ab
0x34b655…2a6f
4 touches
1 conflict
0xbd97c3fe…85d3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc1a4c088…e828
0x34b655…2a6f
4 touches
1 conflict
0x05faf685…a62b
0x34b655…2a6f
2 touches
0 conflicts
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x149ea1fb…e34a
0x34b655…2a6f
2 touches
0 conflicts
0x1d137435…2a8a
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 0x53ca3f7a22…b9a3ab
Audit this contract →
← previous block·next block →recent activity