← previous blocknext block →recent activity
Analyzing
Block #90,833,472
18 transactions · 17 stateful · 2026-07-27 17:39:16 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,833,472 · 18 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
2w05w07w113w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26d1c221…4d2a
0x34b655…2a6f
4 touches
1 conflict
0x61cc3f80…6f64
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0xcb0ead05…32cf
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x1fbae59b…c10f
0x065c9d…c394
2 touches
0 conflicts
0x9607fc4d…921d
0x065c9d…c394
2 touches
0 conflicts
0x9ff176a9…152e
0x065c9d…c394
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 0x26d1c221d7…ef4d2a
Audit this contract →
← previous block·next block →recent activity