← previous blocknext block →recent activity
Analyzing
Block #90,884,472
12 transactions · 10 stateful · 2026-07-27 21:55:51 UTC
Parallelism
58/100
Blocked
60%
Avg conflicts / tx
1.17
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,884,472 · 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
0w01w03w14w25w18w39w410w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69a45f39…39aa
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb7fe0c60…1775
0x34b655…2a6f
6 touches
3 conflicts
0x6925548b…81cc
0x34b655…2a6f
4 touches
1 conflict
0xd6d040d9…9ae3
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0x3da553b9…d669
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 0x69a45f39d6…c739aa
Audit this contract →
← previous block·next block →recent activity