← previous blocknext block →recent activity
Analyzing
Block #90,023,921
15 transactions · 14 stateful · 2026-07-24 21:26:47 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,023,921 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89935301…af69
0x34b655…2a6f
4 touches
1 conflict
0xb416438e…796a
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xf28d07b9…4fb2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x11242505…ceea
0xd32edf…ff58
3 touches
1 conflict
0x3c7c65d0…0b52
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
1 conflict on slot 0x8993530124…aaaf69
Audit this contract →
← previous block·next block →recent activity