← previous blocknext block →recent activity
Analyzing
Block #90,232,813
14 transactions · 13 stateful · 2026-07-25 15:02:35 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,232,813 · 14 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
2w03w15w06w19w010w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x812b1dce…aa12
0x0a2fbf…29b1
4 touches
1 conflict
0x812b1dce…aa13
0x0a2fbf…29b1
4 touches
1 conflict
0x812b1dce…aa16
0x0a2fbf…29b1
4 touches
1 conflict
0x9f4f2d19…1aab
0x0a2fbf…29b1
4 touches
1 conflict
0x9f4f2d19…1aac
0x0a2fbf…29b1
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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: Perpl
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity