← previous blocknext block →recent activity
Analyzing
Block #85,171,327
18 transactions · 16 stateful · 2026-07-02 19:03:26 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,171,327 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w210w115w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3ce9025…da31
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0x7bc74ef3…0fee
0x34b655…2a6f
4 touches
1 conflict
0x7db08ee6…1cba
0x34b655…2a6f
4 touches
1 conflict
0xd2a592d9…1a96
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
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 0xe3ce90252b…a6da31
Audit this contract →
← previous block·next block →recent activity