← previous blocknext block →recent activity
Analyzing
Block #90,689,410
7 transactions · 7 stateful · 2026-07-27 05:34:26 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,689,410 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x6c0e32fc…a6ca
0x34b655…2a6f
4 touches
1 conflict
0x1bdb47ec…864a
0x34b655…2a6f
2 touches
0 conflicts
0x1bdb47ec…864b
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0x5fad6fee64…277714
Audit this contract →
← previous block·next block →recent activity