← previous blocknext block →recent activity
Analyzing
Block #90,113,360
16 transactions · 16 stateful · 2026-07-25 05:00:08 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.88
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,113,360 · 16 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
2w03w14w25w06w17w28w39w213w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0xe0e7ca0f…f67e
0x0a2fbf…29b1
8 touches
6 conflicts
0xe0e7ca0f…f67f
0x0a2fbf…29b1
8 touches
6 conflicts
0xe0e7ca0f…f682
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0x1bff683e…7ecb
0x754704…b603
8 touches
6 conflicts
0x55b4e430…44cb
0x754704…b603
8 touches
6 conflicts
0xaeb9e354…7cc3
0x0a2fbf…29b1
7 touches
6 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 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity