← previous blocknext block →recent activity
Analyzing
Block #90,677,562
12 transactions · 11 stateful · 2026-07-27 04:34:49 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,677,562 · 12 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
3w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86ea50c0…f3a5
0x34b655…2a6f
6 touches
3 conflicts
0x5a100ac0…96d3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53f7214d…8ec6
0x34b655…2a6f
4 touches
1 conflict
0x24b6091e…d294
0x34b655…2a6f
2 touches
0 conflicts
0x3d4c0233…20a5
0x34b655…2a6f
2 touches
0 conflicts
0x4a6982a4…158c
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
3 conflicts on slot 0x86ea50c0e0…8cf3a5
Audit this contract →
← previous block·next block →recent activity