← previous blocknext block →recent activity
Analyzing
Block #90,689,776
9 transactions · 9 stateful · 2026-07-27 05:36:16 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,689,776 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c47f03…f1bb
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
0x34b655…2a6f
4 touches
1 conflict
0xa93fef74…94b3
0x158622…375e
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x11f2aded…153a
0x34b655…2a6f
2 touches
0 conflicts
0x50e54461…beba
0x34b655…2a6f
2 touches
0 conflicts
0x519e0fef…7303
0x34b655…2a6f
2 touches
0 conflicts
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 0x95c47f0322…51f1bb
Audit this contract →
← previous block·next block →recent activity