← previous blocknext block →recent activity
Analyzing
Block #90,977,822
14 transactions · 13 stateful · 2026-07-28 05:45:26 UTC
Parallelism
64/100
Blocked
62%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,977,822 · 14 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
1w02w13w04w15w26w17w28w39w413w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdeee566…3263
0x34b655…2a6f
8 touches
6 conflicts
0x08636046…e60f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x248241b8…7e99
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
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
6 conflicts on slot 0xfdeee56647…f83263
Audit this contract →
← previous block·next block →recent activity