← previous blocknext block →recent activity
Analyzing
Block #90,997,713
8 transactions · 6 stateful · 2026-07-28 07:25:54 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,997,713 · 8 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacd1b162…bee6
0x34b655…2a6f
4 touches
1 conflict
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0x57682f7f…b9fb
0x34b655…2a6f
4 touches
1 conflict
0x0ea00063…777f
0x34b655…2a6f
2 touches
0 conflicts
0x0f3152e8…f181
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x31651485…e008
0x34b655…2a6f
2 touches
0 conflicts
0x4bfdcd51…9b58
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 0xacd1b16256…3bbee6
Audit this contract →
← previous block·next block →recent activity