← previous blocknext block →recent activity
Analyzing
Block #90,839,488
10 transactions · 9 stateful · 2026-07-27 18:09:32 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,839,488 · 10 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
1w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a8482cc…8bee
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xe2e52e46…0894
0x34b655…2a6f
4 touches
1 conflict
0xebb7c1dd…d826
0x34b655…2a6f
4 touches
1 conflict
0xd05fe8f5…892d
0x34b655…2a6f
3 touches
1 conflict
0x08330b36…ae29
0x34b655…2a6f
2 touches
0 conflicts
0x0939317e…94bf
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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
3 conflicts on slot 0x9a8482cc51…b88bee
Audit this contract →
← previous block·next block →recent activity