← previous blocknext block →recent activity
Analyzing
Block #90,614,587
20 transactions · 17 stateful · 2026-07-26 23:18:01 UTC
Parallelism
75/100
Blocked
59%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,614,587 · 20 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
1w04w05w17w08w19w210w311w412w113w214w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x94b46bd0…e95d
0x34b655…2a6f
4 touches
1 conflict
0xbf78ee7f…e7fd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0ee13be7…7b2c
0x34b655…2a6f
4 touches
1 conflict
0x561ad161…c172
0xa6afd3…d132
4 touches
1 conflict
0xde945aa8…1ad5
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
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity