← previous blocknext block →recent activity
Analyzing
Block #85,847,360
23 transactions · 23 stateful · 2026-07-05 22:06:46 UTC
Parallelism
91/100
Blocked
9%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,847,360 · 23 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
11w015w016w017w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xfa870fe3…0642
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x64f43be8…0842
0x065c9d…c394
4 touches
1 conflict
0xd1fe4c2f…acea
0x065c9d…c394
3 touches
1 conflict
0xddb1f602…61cd
0x065c9d…c394
3 touches
1 conflict
0x27378ed2…65bd
0x3c2269…cf62
2 touches
0 conflicts
0x2b36ecc6…093e
0x3c2269…cf62
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity