← previous blocknext block →recent activity
Analyzing
Block #90,621,470
23 transactions · 21 stateful · 2026-07-26 23:52:38 UTC
Parallelism
74/100
Blocked
67%
Avg conflicts / tx
1.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,621,470 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w38w49w011w112w213w314w415w518w219w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xde945aa8…1ad5
0xa6afd3…d132
4 touches
1 conflict
0xf6deafb5…5c25
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x17e90565…d957
0xa6afd3…d132
4 touches
1 conflict
0x561ad161…c172
0xa6afd3…d132
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: 0x48cba278…e2b48b
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity