← previous blocknext block →recent activity
Analyzing
Block #90,678,808
18 transactions · 16 stateful · 2026-07-27 04:41:05 UTC
Parallelism
61/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,678,808 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w27w39w411w512w614w115w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70cfbacf…5c46
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x864d29cb…5ee2
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x379dc435…6616
0x34b655…2a6f
6 touches
3 conflicts
0xd325c12e…de44
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x0a005879…de60
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
10 conflicts on slot 0x70cfbacfa4…e85c46
Audit this contract →
← previous block·next block →recent activity