← previous blocknext block →recent activity
Analyzing
Block #85,158,990
26 transactions · 19 stateful · 2026-07-02 17:41:26 UTC
Parallelism
85/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,158,990 · 26 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
2w04w05w18w09w110w217w218w320w021w122w223w324w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x731e6d82…2883
0x065c9d…c394
6 touches
3 conflicts
0xf5b84d62…d701
0xd32edf…ff58
5 touches
3 conflicts
0x06aed19e…ca57
0x34b655…2a6f
4 touches
1 conflict
0x0ebf1be1…1294
0x34b655…2a6f
4 touches
1 conflict
0x40b5f387…a164
0x34b655…2a6f
4 touches
1 conflict
0x4e8e04e5…89f0
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity