← previous blocknext block →recent activity
Analyzing
Block #86,751,861
32 transactions · 29 stateful · 2026-07-10 02:49:17 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,751,861 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w211w215w016w117w018w219w323w125w330w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x794443d1…2190
0x34b655…2a6f
8 touches
6 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
8 touches
6 conflicts
0x6fee072d…ac0a
0xd32edf…ff58
7 touches
6 conflicts
0x9a555477…19a8
0x754704…b603
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 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: Perpl
6 conflicts on slot 0x794443d183…2e2190
Audit this contract →
← previous block·next block →recent activity