← previous blocknext block →recent activity
Analyzing
Block #86,351,320
10 transactions · 8 stateful · 2026-07-08 06:10:06 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,351,320 · 10 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
2w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8dbb148…445b
0x34b655…2a6f
4 touches
1 conflict
0xedf4636f…b2a2
0x34b655…2a6f
4 touches
1 conflict
0x3eee9603…a91d
0x065c9d…c394
2 touches
0 conflicts
0x4ec998b0…d433
0x065c9d…c394
2 touches
0 conflicts
0xb9ba8ccb…ddff
0x065c9d…c394
2 touches
0 conflicts
0xc5bb15a4…1122
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
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 0xf8dbb148cb…eb445b
Audit this contract →
← previous block·next block →recent activity