← previous blocknext block →recent activity
Analyzing
Block #85,513,439
15 transactions · 14 stateful · 2026-07-04 09:01:51 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,513,439 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x46ccf4b4…014b
0xa6afd3…d132
4 touches
1 conflict
0xb68e226d…c054
0xa6afd3…d132
4 touches
1 conflict
0xc3cda232…10dd
0x34b655…2a6f
4 touches
1 conflict
0xce2b3a4c…2c38
0x40c49f…2af0
2 touches
0 conflicts
0xfc9d7100…7e7e
0x40c49f…2af0
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
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity