← previous blocknext block →recent activity
Analyzing
Block #90,821,831
16 transactions · 13 stateful · 2026-07-27 16:40:42 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,821,831 · 16 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
1w02w17w09w111w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa88a59cd…35ac
0x34b655…2a6f
4 touches
1 conflict
0x449d101e…ea3f
0xa6afd3…d132
4 touches
1 conflict
0x2ecb2d6f…2430
0xa6afd3…d132
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0fffa5c0…a3a9
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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
1 conflict on slot 0xa88a59cd59…a435ac
Audit this contract →
← previous block·next block →recent activity