← previous blocknext block →recent activity
Analyzing
Block #86,813,723
23 transactions · 16 stateful · 2026-07-10 09:42:21 UTC
Parallelism
87/100
Blocked
19%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,813,723 · 23 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
2w05w115w017w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfc58aa8…e1df
0x34b655…2a6f
4 touches
1 conflict
0x00578320…1ba0
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x226e3b61…5e6f
0x34b655…2a6f
4 touches
1 conflict
0x823a3658…acf6
0x34b655…2a6f
4 touches
1 conflict
0x95d63682…276c
0x34b655…2a6f
4 touches
1 conflict
0x95d63682…276d
0x34b655…2a6f
4 touches
1 conflict
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 0xdfc58aa8cc…17e1df
Audit this contract →
← previous block·next block →recent activity