← previous blocknext block →recent activity
Analyzing
Block #86,232,867
21 transactions · 19 stateful · 2026-07-07 16:59:08 UTC
Parallelism
81/100
Blocked
37%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,232,867 · 21 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
4w05w17w08w19w212w013w115w318w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94de4d05…ad01
0x34b655…2a6f
8 touches
6 conflicts
0x54fc1ac2…a311
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x7fcd31f6…cafb
0x34b655…2a6f
6 touches
3 conflicts
0xac0b4a08…faae
0x34b655…2a6f
6 touches
3 conflicts
0xbcc5ae85…6ba2
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x23a320fb…cbd7
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
6 conflicts on slot 0x94de4d05c1…d4ad01
Audit this contract →
← previous block·next block →recent activity