← previous blocknext block →recent activity
Analyzing
Block #90,812,263
12 transactions · 11 stateful · 2026-07-27 15:52:33 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,812,263 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w18w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6b9bb4b…145a
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x73320e64…b06f
0x34b655…2a6f
4 touches
1 conflict
0x17a5bb2a…4271
0x34b655…2a6f
2 touches
0 conflicts
0x1aa62c36…420a
0x34b655…2a6f
2 touches
0 conflicts
0x23c9c7bf…4e33
0x34b655…2a6f
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: Perpl
1 conflict on slot 0xc6b9bb4b8d…cc145a
Audit this contract →
← previous block·next block →recent activity