← previous blocknext block →recent activity
Analyzing
Block #85,179,800
28 transactions · 18 stateful · 2026-07-02 19:59:56 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,179,800 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w013w014w117w119w220w321w224w425w526w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x822f8512…68e0
0x34b655…2a6f
10 touches
10 conflicts
0xf2da0602…3d7a
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3230277c…ef39
0xc8689a…ee79
4 touches
1 conflict
0x022b49db…a477
0x34b655…2a6f
4 touches
1 conflict
0x3923cd2c…e6d3
0x34b655…2a6f
4 touches
1 conflict
0x5737d14a…93a2
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 0x822f8512e8…4668e0
Audit this contract →
← previous block·next block →recent activity