← previous blocknext block →recent activity
Analyzing
Block #85,993,873
32 transactions · 27 stateful · 2026-07-06 14:23:40 UTC
Parallelism
88/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,993,873 · 32 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
3w04w05w18w013w114w019w120w121w222w327w128w029w130w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x1e9dac68…ef8d
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0xed73ded0…69a7
0x065c9d…c394
4 touches
1 conflict
0x006c3b86…59a9
0x34b655…2a6f
4 touches
1 conflict
0x16be067e…1565
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity