← previous blocknext block →recent activity
Analyzing
Block #90,820,101
30 transactions · 27 stateful · 2026-07-27 16:32:00 UTC
Parallelism
80/100
Blocked
67%
Avg conflicts / tx
1.37
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,820,101 · 30 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
2w03w14w26w07w18w29w310w412w314w415w016w117w218w319w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x0fffa5c0…a3a9
0xa6afd3…d132
10 touches
10 conflicts
0x731f2745…9370
0xa6afd3…d132
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xdb067026…9eb8
0x2b46c0…1669
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4cabb80a…46bf
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: 0x48cba278…e2b48b
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity