← previous blocknext block →recent activity
Analyzing
Block #86,850,902
33 transactions · 19 stateful · 2026-07-10 13:51:02 UTC
Parallelism
79/100
Blocked
63%
Avg conflicts / tx
0.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,850,902 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w110w213w314w115w216w329w330w431w532w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xf81d0d0f…cf78
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0f4d9f2d…ac65
0x34b655…2a6f
5 touches
3 conflicts
0x4c13c80e…d834
0x40c49f…2af0
4 touches
1 conflict
0x81c4611b…dde6
0x40c49f…2af0
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity