← previous blocknext block →recent activity
Analyzing
Block #90,386,799
15 transactions · 15 stateful · 2026-07-26 04:05:58 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,386,799 · 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
4w05w06w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xe0153faf…33ca
0x34b655…2a6f
8 touches
6 conflicts
0x34933aba…06e4
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xfb70218e…3367
0x34b655…2a6f
6 touches
3 conflicts
0x27034002…2f27
0x34b655…2a6f
6 touches
3 conflicts
0xae9672be…685f
0x34b655…2a6f
6 touches
3 conflicts
0xc5ee648c…d69a
0x34b655…2a6f
6 touches
3 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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity