← previous blocknext block →recent activity
Analyzing
Block #90,992,582
17 transactions · 16 stateful · 2026-07-28 06:59:50 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,992,582 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w17w28w39w210w411w515w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab1d6786…884e
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x8cd684d0…c3cb
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x3f4f9f22…8ad7
0x34b655…2a6f
6 touches
3 conflicts
0xc576a23c…4aba
0x34b655…2a6f
6 touches
3 conflicts
0xb5a1ebf7…bd5f
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
10 conflicts on slot 0xab1d678652…cf884e
Audit this contract →
← previous block·next block →recent activity