← previous blocknext block →recent activity
Analyzing
Block #90,876,915
12 transactions · 12 stateful · 2026-07-27 21:17:50 UTC
Parallelism
58/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,876,915 · 12 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
2w04w15w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xd7908b5f…56b9
0x34b655…2a6f
4 touches
1 conflict
0xef71557f…1de8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x31ba5616…4601
0x34b655…2a6f
4 touches
1 conflict
0x38c6ff01…689f
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
1 conflict on slot 0xfaf89f4544…89ced6
Audit this contract →
← previous block·next block →recent activity