← previous blocknext block →recent activity
Analyzing
Block #85,987,356
34 transactions · 20 stateful · 2026-07-06 13:40:04 UTC
Parallelism
88/100
Blocked
40%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,987,356 · 34 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
2w03w04w114w015w118w020w121w122w023w124w230w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1791476…927a
0x34b655…2a6f
4 touches
1 conflict
0x7e10454f…4d9e
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0x08d66073…e706
0x34b655…2a6f
4 touches
1 conflict
0x0aa213f0…5300
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
1 conflict on slot 0xe179147640…12927a
Audit this contract →
← previous block·next block →recent activity