← previous blocknext block →recent activity
Analyzing
Block #90,817,122
11 transactions · 11 stateful · 2026-07-27 16:17:01 UTC
Parallelism
73/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,817,122 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96efe05d…5d48
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0xf0cb1341…de0a
0x34b655…2a6f
4 touches
1 conflict
0x19cfd958…9c8c
0x34b655…2a6f
2 touches
0 conflicts
0x38948e75…437a
0x34b655…2a6f
2 touches
0 conflicts
0x42c7fd6d…fc6c
0x34b655…2a6f
2 touches
0 conflicts
0x4688dd30…ef52
0x34b655…2a6f
2 touches
0 conflicts
0x4c188934…158e
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 0x96efe05d27…da5d48
Audit this contract →
← previous block·next block →recent activity