← previous blocknext block →recent activity
Analyzing
Block #86,151,776
18 transactions · 16 stateful · 2026-07-07 07:57:42 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.56
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,151,776 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w112w213w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
12 touches
15 conflicts
0x680fdd59…e84d
0x34b655…2a6f
6 touches
3 conflicts
0x4eb98096…65c2
0x34b655…2a6f
5 touches
3 conflicts
0x72ec3615…68d4
0x34b655…2a6f
5 touches
3 conflicts
0x663d3288…f460
0x34b655…2a6f
5 touches
3 conflicts
0x517d35c7…f359
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
21 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity