← previous blocknext block →recent activity
Analyzing
Block #90,288,080
12 transactions · 12 stateful · 2026-07-25 19:41:42 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,288,080 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb10db32e…d5de
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0x55b4e430…44cb
0x754704…b603
8 touches
6 conflicts
0xb10db32e…d5da
0x0a2fbf…29b1
8 touches
6 conflicts
0xb10db32e…d5db
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
6 touches
3 conflicts
0x1bff683e…7ecb
0x754704…b603
6 touches
3 conflicts
0x158401b3…d392
0x0a2fbf…29b1
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
6 conflicts on slot 0xb10db32e69…41d5de
Audit this contract →
← previous block·next block →recent activity