← previous blocknext block →recent activity
Analyzing
Block #90,276,930
15 transactions · 13 stateful · 2026-07-25 18:45:04 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,276,930 · 15 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
1w02w13w05w06w17w18w29w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0x0a7896d4…be7c
0x0a2fbf…29b1
6 touches
3 conflicts
0x0a7896d4…be7d
0x0a2fbf…29b1
6 touches
3 conflicts
0x567eb89c…59b9
0x0a2fbf…29b1
6 touches
3 conflicts
0x567eb89c…59ba
0x0a2fbf…29b1
6 touches
3 conflicts
0x567eb89c…59bd
0x0a2fbf…29b1
6 touches
3 conflicts
0x1416e2fb…e2b3
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 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
3 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity