← previous blocknext block →recent activity
Analyzing
Block #86,214,795
28 transactions · 23 stateful · 2026-07-07 14:58:27 UTC
Parallelism
79/100
Blocked
30%
Avg conflicts / tx
0.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,214,795 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w09w114w016w122w123w224w325w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x5fe7e126…6dd2
0x34b655…2a6f
6 touches
3 conflicts
0x72470f81…c402
0x34b655…2a6f
4 touches
1 conflict
0x931619e4…3b17
0x34b655…2a6f
4 touches
1 conflict
0xa233e6a5…5939
0x34b655…2a6f
4 touches
1 conflict
0xaa2940af…5397
0x34b655…2a6f
4 touches
1 conflict
0xc5a1b2fe…5369
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity