← previous blocknext block →recent activity
Analyzing
Block #85,897,332
17 transactions · 13 stateful · 2026-07-06 03:39:35 UTC
Parallelism
65/100
Blocked
54%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,897,332 · 17 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
1w02w03w05w16w18w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc25f1e5…2cac
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc12a9d89…e9b6
0x34b655…2a6f
6 touches
3 conflicts
0x207cc41e…57c6
0x34b655…2a6f
6 touches
3 conflicts
0x397501e2…9a12
0x34b655…2a6f
6 touches
3 conflicts
0x27f085dd…5bae
0x34b655…2a6f
4 touches
1 conflict
0x3649cb8c…b8f9
0x34b655…2a6f
4 touches
1 conflict
0x3f100ff5…d5af
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 0xcc25f1e531…5f2cac
Audit this contract →
← previous block·next block →recent activity