← previous blocknext block →recent activity
Analyzing
Block #90,849,933
21 transactions · 19 stateful · 2026-07-27 19:02:04 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,849,933 · 21 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
3w04w15w26w09w310w412w513w617w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x898d9b8a…d1ef
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6426
0x34b655…2a6f
10 touches
10 conflicts
0x588380ee…0a5c
0x34b655…2a6f
8 touches
6 conflicts
0x19ebfd29…e80e
0x34b655…2a6f
8 touches
6 conflicts
0x08d1d6b7…4bb3
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity