← previous blocknext block →recent activity
Analyzing
Block #90,773,116
24 transactions · 20 stateful · 2026-07-27 12:35:30 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,773,116 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w07w18w210w311w112w215w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8a2be43d…8c49
0x065c9d…c394
2 touches
0 conflicts
0xb43e8b79…f39e
0x065c9d…c394
2 touches
0 conflicts
0xce085aff…cbf4
0x065c9d…c394
2 touches
0 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
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity