← previous blocknext block →recent activity
Analyzing
Block #90,239,230
17 transactions · 16 stateful · 2026-07-25 15:34:53 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,239,230 · 17 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
1w02w14w05w16w18w212w213w314w415w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0x7aad02c6…b979
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0d2de0f6…e6c6
0x34b655…2a6f
4 touches
1 conflict
0x1de49243…4aa3
0x34b655…2a6f
4 touches
1 conflict
0x345f75e4…71a0
0x34b655…2a6f
4 touches
1 conflict
0x3a9c09a5…aa17
0x34b655…2a6f
4 touches
1 conflict
0x4d1c2806…5947
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity