← previous blocknext block →recent activity
Analyzing
Block #90,836,247
20 transactions · 16 stateful · 2026-07-27 17:53:14 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,836,247 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w27w38w09w110w416w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xfb31d278…9107
0x34b655…2a6f
8 touches
6 conflicts
0x8f203394…f2db
0x34b655…2a6f
6 touches
3 conflicts
0x4fd5c2d2…3afc
0x34b655…2a6f
4 touches
1 conflict
0x56e254bc…1215
0x34b655…2a6f
4 touches
1 conflict
0x68357b32…46fc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity