← previous blocknext block →recent activity
Analyzing
Block #86,492,792
13 transactions · 9 stateful · 2026-07-08 21:55:41 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,492,792 · 13 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
1w04w05w17w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f34fd08…aeb3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd89daad2…48b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0xd2961c76…b18e
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 0x5f34fd08e4…a5aeb3
Audit this contract →
← previous block·next block →recent activity