← previous blocknext block →recent activity
Analyzing
Block #90,890,965
13 transactions · 10 stateful · 2026-07-27 22:28:31 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,890,965 · 13 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
1w02w03w14w26w18w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa93c5a4e…7108
0x34b655…2a6f
8 touches
6 conflicts
0xc6000ba5…8d65
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x0aa5e418…5d1d
0x34b655…2a6f
4 touches
1 conflict
0x10379e8d…3675
0x34b655…2a6f
4 touches
1 conflict
0x37d710c8…45c1
0x34b655…2a6f
4 touches
1 conflict
0x46ee3c65…4ab8
0x34b655…2a6f
4 touches
1 conflict
0x6771eae2…7014
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 0xa93c5a4e3a…137108
Audit this contract →
← previous block·next block →recent activity