← previous blocknext block →recent activity
Analyzing
Block #90,894,558
19 transactions · 18 stateful · 2026-07-27 22:46:35 UTC
Parallelism
63/100
Blocked
39%
Avg conflicts / tx
0.89
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,894,558 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w211w312w414w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94907e1c…f808
0x34b655…2a6f
10 touches
10 conflicts
0x2d651956…12e8
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x3ca268be…8865
0x34b655…2a6f
4 touches
1 conflict
0x52b477bc…7ccf
0x34b655…2a6f
4 touches
1 conflict
0x640b61a9…cda9
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x94907e1c19…9af808
Audit this contract →
← previous block·next block →recent activity