← previous blocknext block →recent activity
Analyzing
Block #90,892,985
15 transactions · 15 stateful · 2026-07-27 22:38:40 UTC
Parallelism
87/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,892,985 · 15 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
1w02w03w14w05w16w07w18w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb566cc65…214d
0xa6afd3…d132
4 touches
1 conflict
0x0382fe33…4c5f
0x34b655…2a6f
4 touches
1 conflict
0x2283674e…f086
0x34b655…2a6f
4 touches
1 conflict
0x30d58b0b…8806
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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: Kuru Exchange: Market-WETH/USDC
1 conflict on slot 0xb566cc65b9…bf214d
Audit this contract →
← previous block·next block →recent activity