← previous blocknext block →recent activity
Analyzing
Block #90,851,005
18 transactions · 16 stateful · 2026-07-27 19:07:27 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,851,005 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w08w19w212w313w114w215w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96ed2d2d…2690
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8218911e…3bed
0x34b655…2a6f
6 touches
3 conflicts
0x26d1c221…4d2a
0x34b655…2a6f
6 touches
3 conflicts
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x61cc3f80…6f64
0x34b655…2a6f
4 touches
1 conflict
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
3 conflicts on slot 0x96ed2d2d23…d92690
Audit this contract →
← previous block·next block →recent activity