← previous blocknext block →recent activity
Analyzing
Block #90,884,419
14 transactions · 13 stateful · 2026-07-27 21:55:35 UTC
Parallelism
43/100
Blocked
54%
Avg conflicts / tx
1.86
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,884,419 · 14 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
2w03w14w27w38w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xa6b48d6e…0705
0x34b655…2a6f
8 touches
6 conflicts
0x69a45f39…39aa
0x34b655…2a6f
8 touches
6 conflicts
0xfcfb570f…cf1c
0x34b655…2a6f
6 touches
3 conflicts
0x1e56f6b6…5940
0x34b655…2a6f
6 touches
3 conflicts
0x23e706b3…0e16
0x34b655…2a6f
6 touches
3 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity