← previous blocknext block →recent activity
Analyzing
Block #85,513,423
21 transactions · 16 stateful · 2026-07-04 09:01:44 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,513,423 · 21 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
1w02w13w24w05w18w09w113w114w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30faf03c…78b1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xb68e226d…c054
0xa6afd3…d132
6 touches
3 conflicts
0xca0f0668…caf3
0xa6afd3…d132
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x1198bb76…f50f
0x40c49f…2af0
4 touches
1 conflict
0xfc9d7100…7e7e
0x40c49f…2af0
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 0x30faf03c2d…0178b1
Audit this contract →
← previous block·next block →recent activity