← previous blocknext block →recent activity
Analyzing
Block #90,116,800
16 transactions · 16 stateful · 2026-07-25 05:17:37 UTC
Parallelism
50/100
Blocked
44%
Avg conflicts / tx
1.75
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,116,800 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e2998c5…9024
0x0a2fbf…29b1
16 touches
28 conflicts
0x2e2998c5…9025
0x0a2fbf…29b1
16 touches
28 conflicts
0x00000000…0005
0x370e2e…63b4
16 touches
28 conflicts
0xc4da12a5…3d9e
0x370e2e…63b4
16 touches
28 conflicts
0x2e2998c5…9028
0x0a2fbf…29b1
16 touches
28 conflicts
0xa30a222d…4a91
0x0a2fbf…29b1
16 touches
28 conflicts
0xa30a222d…4a92
0x0a2fbf…29b1
16 touches
28 conflicts
0x1bff683e…7ecb
0x754704…b603
16 touches
28 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
28 conflicts on slot 0x2e2998c54c…e09024
Audit this contract →
← previous block·next block →recent activity