← previous blocknext block →recent activity
Analyzing
Block #90,771,350
10 transactions · 9 stateful · 2026-07-27 12:26:37 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,771,350 · 10 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xe21a94dd…4838
0x34b655…2a6f
3 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x8b7af792…9ef0
0x34b655…2a6f
2 touches
0 conflicts
0xa3f095f5…bd87
0x34b655…2a6f
2 touches
0 conflicts
0xb06a48e8…d6d1
0x34b655…2a6f
2 touches
0 conflicts
0xb1b21ea8…d790
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 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity