← previous blocknext block →recent activity
Analyzing
Block #86,961,417
23 transactions · 19 stateful · 2026-07-11 02:09:49 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,961,417 · 23 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
1w05w08w09w112w113w114w215w117w318w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd5f87b76…6d70
0x065c9d…c394
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x2170bea4…4723
0x34b655…2a6f
4 touches
1 conflict
0x4681609f…6493
0x34b655…2a6f
4 touches
1 conflict
0x535cd929…07ce
0x34b655…2a6f
4 touches
1 conflict
0x77d99233…7634
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity