← previous blocknext block →recent activity
Analyzing
Block #86,856,452
16 transactions · 13 stateful · 2026-07-10 14:28:09 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,856,452 · 16 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
4w05w16w28w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11d629eb…bcd9
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x288bc578…318e
0x34b655…2a6f
4 touches
1 conflict
0x4327afd2…1b3a
0x34b655…2a6f
4 touches
1 conflict
0x44968aef…ada1
0x34b655…2a6f
4 touches
1 conflict
0x71658d1a…f1ec
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
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
3 conflicts on slot 0x11d629ebd0…9fbcd9
Audit this contract →
← previous block·next block →recent activity