← previous blocknext block →recent activity
Analyzing
Block #90,023,832
18 transactions · 16 stateful · 2026-07-24 21:26:20 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,023,832 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w06w18w211w012w113w214w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a5d321d…a474
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x84ca6bbf…3b56
0x34b655…2a6f
6 touches
3 conflicts
0x3030ee21…ab78
0xd32edf…ff58
5 touches
3 conflicts
0x7b211ab8…e32c
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x0933b65e…e7d4
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: Perpl
6 conflicts on slot 0x1a5d321d5d…0da474
Audit this contract →
← previous block·next block →recent activity