← previous blocknext block →recent activity
Analyzing
Block #90,888,364
7 transactions · 7 stateful · 2026-07-27 22:15:26 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,888,364 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8416783…02fd
0x34b655…2a6f
4 touches
1 conflict
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0x6d955786…1327
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2bfb71b5…3a04
0x34b655…2a6f
2 touches
0 conflicts
0x2bfb71b5…3a05
0x34b655…2a6f
2 touches
0 conflicts
0x8f203394…f2dc
0x34b655…2a6f
2 touches
0 conflicts
0x35b0198e…3e0d
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 0xf841678382…9e02fd
Audit this contract →
← previous block·next block →recent activity