← previous blocknext block →recent activity
Analyzing
Block #86,978,823
14 transactions · 14 stateful · 2026-07-11 04:06:05 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,978,823 · 14 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
1w02w14w05w18w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b75f0c2…d323
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x3a1edb3e…b841
0x34b655…2a6f
4 touches
1 conflict
0x44231245…5442
0x34b655…2a6f
4 touches
1 conflict
0x82ffcf2f…491d
0x34b655…2a6f
4 touches
1 conflict
0xc55a9a20…89ac
0x34b655…2a6f
4 touches
1 conflict
0xcbe18c62…3a5c
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 0x6b75f0c27b…f5d323
Audit this contract →
← previous block·next block →recent activity