← previous blocknext block →recent activity
Analyzing
Block #86,957,936
36 transactions · 25 stateful · 2026-07-11 01:46:32 UTC
Parallelism
89/100
Blocked
32%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,957,936 · 36 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w09w010w011w115w116w217w118w221w022w127w028w234w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6ed530c…d450
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x123a6fe2…d527
0x34b655…2a6f
4 touches
1 conflict
0x2b7950c1…2342
0x34b655…2a6f
4 touches
1 conflict
0x6630d365…74ad
0x34b655…2a6f
4 touches
1 conflict
0x67a9f76d…0b84
0x34b655…2a6f
4 touches
1 conflict
0x67a9f76d…0b85
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
3 conflicts on slot 0xb6ed530c56…eed450
Audit this contract →
← previous block·next block →recent activity