← previous blocknext block →recent activity
Analyzing
Block #85,219,410
14 transactions · 12 stateful · 2026-07-03 00:23:44 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,219,410 · 14 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
1w02w13w04w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bdb9869…7558
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2c29821f…f5d7
0x065c9d…c394
2 touches
0 conflicts
0x2f949e6e…c792
0x065c9d…c394
2 touches
0 conflicts
0x4abbce95…40b3
0x065c9d…c394
2 touches
0 conflicts
0x6cf022d9…5c02
0x065c9d…c394
2 touches
0 conflicts
0x73e3b124…0f62
0x065c9d…c394
2 touches
0 conflicts
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 0x6bdb9869c7…427558
Audit this contract →
← previous block·next block →recent activity