← previous blocknext block →recent activity
Analyzing
Block #85,129,189
22 transactions · 19 stateful · 2026-07-02 14:22:44 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,129,189 · 22 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
2w05w16w28w09w112w014w017w218w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7fffd49d…772a
0x34b655…2a6f
6 touches
3 conflicts
0x67d8b378…f2f8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x3a98d8f0…1882
0x34b655…2a6f
4 touches
1 conflict
0x3c167411…e1ef
0x34b655…2a6f
4 touches
1 conflict
0x3dfdb97e…0723
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity