← previous blocknext block →recent activity
Analyzing
Block #85,185,433
19 transactions · 19 stateful · 2026-07-02 20:37:30 UTC
Parallelism
58/100
Blocked
53%
Avg conflicts / tx
0.74
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,185,433 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w17w08w19w210w311w412w513w614w016w117w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x056ec16c…55b9
0x34b655…2a6f
4 touches
1 conflict
0x05b18b8f…e055
0x34b655…2a6f
4 touches
1 conflict
0x2b32c554…178e
0x34b655…2a6f
4 touches
1 conflict
0x398dcfc7…8cc9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51a914cf…a822
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity