← previous blocknext block →recent activity
Analyzing
Block #90,816,901
13 transactions · 13 stateful · 2026-07-27 16:15:54 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,816,901 · 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x996f3d91…1a7c
0x34b655…2a6f
4 touches
1 conflict
0x673891f1…bf47
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0bcac816…a452
0x34b655…2a6f
2 touches
0 conflicts
0x1050fef5…54e5
0x34b655…2a6f
2 touches
0 conflicts
0x1b1451d3…e1f4
0x34b655…2a6f
2 touches
0 conflicts
0x1f384197…7b58
0x34b655…2a6f
2 touches
0 conflicts
0x1ffbc5c9…461f
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 0x996f3d91c2…481a7c
Audit this contract →
← previous block·next block →recent activity