← previous blocknext block →recent activity
Analyzing
Block #90,330,368
19 transactions · 17 stateful · 2026-07-25 23:16:38 UTC
Parallelism
79/100
Blocked
24%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,330,368 · 19 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
1w02w15w06w111w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96dd83e6…a507
0x34b655…2a6f
8 touches
6 conflicts
0x60270642…c780
0x34b655…2a6f
6 touches
3 conflicts
0xff8b4178…773d
0x34b655…2a6f
6 touches
3 conflicts
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0x3726966a…669d
0x34b655…2a6f
4 touches
1 conflict
0x38f504a9…a8bf
0x34b655…2a6f
4 touches
1 conflict
0x4560e5a8…b741
0x34b655…2a6f
4 touches
1 conflict
0x5b145de0…367c
0xc8689a…ee79
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 0x96dd83e650…3fa507
Audit this contract →
← previous block·next block →recent activity