← previous blocknext block →recent activity
Analyzing
Block #90,288,033
20 transactions · 17 stateful · 2026-07-25 19:41:27 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,288,033 · 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
4w05w16w27w310w011w112w213w314w416w318w019w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
10 touches
10 conflicts
0x158401b3…d391
0x0a2fbf…29b1
10 touches
10 conflicts
0x158401b3…d392
0x0a2fbf…29b1
10 touches
10 conflicts
0xb10db32e…d5da
0x0a2fbf…29b1
10 touches
10 conflicts
0xb10db32e…d5db
0x0a2fbf…29b1
10 touches
10 conflicts
0xb10db32e…d5de
0x0a2fbf…29b1
10 touches
10 conflicts
0x00000000…0005
0x370e2e…63b4
10 touches
10 conflicts
0x1bff683e…7ecb
0x754704…b603
10 touches
10 conflicts
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
10 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity