← previous blocknext block →recent activity
Analyzing
Block #85,136,339
18 transactions · 14 stateful · 2026-07-02 15:10:29 UTC
Parallelism
89/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,136,339 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60e0d54b…398f
0x34b655…2a6f
4 touches
1 conflict
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xe5a02384…d946
0x065c9d…c394
3 touches
1 conflict
0xa980598e…ec52
0x3bd359…433a
2 touches
0 conflicts
0x9eb5f91a…a879
0x754704…b603
2 touches
0 conflicts
0x95d068d1…562c
0xa6afd3…d132
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 0x60e0d54b34…74398f
Audit this contract →
← previous block·next block →recent activity