← previous blocknext block →recent activity
Analyzing
Block #90,796,063
22 transactions · 18 stateful · 2026-07-27 14:30:58 UTC
Parallelism
68/100
Blocked
67%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,796,063 · 22 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
2w03w18w09w110w211w312w413w114w515w618w119w220w421w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6818217…345a
0x34b655…2a6f
8 touches
6 conflicts
0xa3f6f7c8…2436
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x742436a7…c4d4
0x34b655…2a6f
6 touches
3 conflicts
0x9fd372a1…a959
0x34b655…2a6f
6 touches
3 conflicts
0x7244e2f4…e56e
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
6 conflicts on slot 0xf68182176b…05345a
Audit this contract →
← previous block·next block →recent activity