← previous blocknext block →recent activity
Analyzing
Block #90,288,137
13 transactions · 13 stateful · 2026-07-25 19:42:00 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,288,137 · 13 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
2w05w06w07w18w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x158401b3…d391
0x0a2fbf…29b1
4 touches
1 conflict
0x158401b3…d392
0x0a2fbf…29b1
4 touches
1 conflict
0xb10db32e…d5da
0x0a2fbf…29b1
4 touches
1 conflict
0xb10db32e…d5db
0x0a2fbf…29b1
4 touches
1 conflict
0xb10db32e…d5de
0x0a2fbf…29b1
4 touches
1 conflict
0x0bb0061e…dfbc
0x34b655…2a6f
4 touches
1 conflict
0x5e0b8bbe…377b
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: 0x0a2fbf2d…f729b1
1 conflict on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity