← previous blocknext block →recent activity
Analyzing
Block #85,760,829
22 transactions · 18 stateful · 2026-07-05 12:30:25 UTC
Parallelism
68/100
Blocked
33%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,760,829 · 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
3w010w011w114w215w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
8 touches
6 conflicts
0x90d81b88…3a34
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x61684cf2…e923
0x34b655…2a6f
6 touches
3 conflicts
0x8ea5a2b1…7a88
0x34b655…2a6f
6 touches
3 conflicts
0x309ef367…e8a1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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