← previous blocknext block →recent activity
Analyzing
Block #90,990,571
13 transactions · 13 stateful · 2026-07-28 06:49:39 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,990,571 · 13 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
8w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c0d708e…f3d2
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…642d
0x34b655…2a6f
4 touches
1 conflict
0xfa3d71b4…937f
0x34b655…2a6f
4 touches
1 conflict
0xfb70218e…3367
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x641aed07…bcb9
0x34b655…2a6f
4 touches
1 conflict
0x7281cd97…f967
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
6 conflicts on slot 0x6c0d708e8c…35f3d2
Audit this contract →
← previous block·next block →recent activity