← previous blocknext block →recent activity
Analyzing
Block #90,539,923
24 transactions · 20 stateful · 2026-07-26 17:02:24 UTC
Parallelism
88/100
Blocked
50%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,539,923 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w17w08w19w012w114w015w016w117w218w119w122w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0xf96c388b…7c4d
0xa6afd3…d132
4 touches
1 conflict
0x89678d1b…463e
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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: 0x48cba278…e2b48b
1 conflict on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity