← previous blocknext block →recent activity
Analyzing
Block #86,132,943
18 transactions · 17 stateful · 2026-07-07 05:51:59 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,132,943 · 18 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
1w02w13w24w05w16w212w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52c63247…ce02
0x0a3323…0a3c
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xff3addfc…633e
0x6f4756…dd5b
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xffa7d0a4…b10a
0x40c49f…2af0
4 touches
1 conflict
0x446f2734…8b54
0x0a3323…0a3c
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xfaa368b0…baac
0x40c49f…2af0
2 touches
0 conflicts
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: 0x0a332311…6e0a3c
3 conflicts on slot 0x52c63247e1…bace02
Audit this contract →
← previous block·next block →recent activity