← previous blocknext block →recent activity
Analyzing
Block #90,625,488
15 transactions · 15 stateful · 2026-07-27 00:12:51 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,625,488 · 15 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
3w04w15w26w39w411w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
4 touches
1 conflict
0x4560e5a8…b741
0x34b655…2a6f
4 touches
1 conflict
0x1dafc5cd…f56f
0x34b655…2a6f
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x679705f0…4531
0x34b655…2a6f
2 touches
0 conflicts
0x7634a3f4…7f24
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity