← previous blocknext block →recent activity
Analyzing
Block #85,167,533
26 transactions · 24 stateful · 2026-07-02 18:38:15 UTC
Parallelism
88/100
Blocked
42%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,167,533 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w27w08w09w010w111w112w215w118w119w120w224w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x56a919c4…ab49
0xee8c0e…1242
6 touches
3 conflicts
0x70638c24…1553
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x176e82bc…b152
0x065c9d…c394
5 touches
3 conflicts
0xc1aad6e5…9135
0x34b655…2a6f
5 touches
3 conflicts
0x06aed19e…ca57
0x34b655…2a6f
4 touches
1 conflict
0x3ed01bdd…b317
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
3 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity