← previous blocknext block →recent activity
Analyzing
Block #85,354,693
18 transactions · 17 stateful · 2026-07-03 15:24:51 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,354,693 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w07w18w110w112w114w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x316d90ef…fe4a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0x91541bd7…e6d8
0x34b655…2a6f
4 touches
1 conflict
0xbc0cf3d2…0451
0x34b655…2a6f
4 touches
1 conflict
0xd7db8c21…9e40
0x34b655…2a6f
4 touches
1 conflict
0xefcdf197…96a2
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 0x316d90ef81…9dfe4a
Audit this contract →
← previous block·next block →recent activity