← previous blocknext block →recent activity
Analyzing
Block #90,822,698
17 transactions · 17 stateful · 2026-07-27 16:45:04 UTC
Parallelism
76/100
Blocked
24%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,822,698 · 17 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
2w06w17w211w312w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb384cb4…9cde
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x80656e3b…9240
0x34b655…2a6f
6 touches
3 conflicts
0xe1d31a03…6b5e
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xbb384cb450…1b9cde
Audit this contract →
← previous block·next block →recent activity