← previous blocknext block →recent activity
Analyzing
Block #90,849,592
16 transactions · 13 stateful · 2026-07-27 19:00:21 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,849,592 · 16 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
2w04w05w16w07w28w111w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bd95eb4…e562
0x34b655…2a6f
6 touches
3 conflicts
0x16a932ce…fc1c
0x34b655…2a6f
4 touches
1 conflict
0x1ee6a8c8…026f
0x34b655…2a6f
4 touches
1 conflict
0x26fc2b70…04de
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4f394483…ff62
0x34b655…2a6f
4 touches
1 conflict
0x606bc50d…4c10
0x34b655…2a6f
4 touches
1 conflict
0x74eb26c1…d361
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 0x0bd95eb406…f6e562
Audit this contract →
← previous block·next block →recent activity