← previous blocknext block →recent activity
Analyzing
Block #86,967,329
21 transactions · 16 stateful · 2026-07-11 02:49:20 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,967,329 · 21 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
1w03w17w213w015w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdec4fb9a…1d0c
0x34b655…2a6f
4 touches
1 conflict
0x977e7afc…bf14
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xad15ca0d…a3d5
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x050376db…0f47
0x34b655…2a6f
4 touches
1 conflict
0x050376db…0f48
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 0xdec4fb9ac9…ce1d0c
Audit this contract →
← previous block·next block →recent activity