← previous blocknext block →recent activity
Analyzing
Block #86,300,399
22 transactions · 18 stateful · 2026-07-08 00:29:57 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
0.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,300,399 · 22 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
1w02w03w14w25w17w08w115w016w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x966e45cf…0f25
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xc5a1b2fe…5369
0x34b655…2a6f
6 touches
3 conflicts
0x5f752320…7f90
0x34b655…2a6f
4 touches
1 conflict
0x6637e421…af93
0x34b655…2a6f
4 touches
1 conflict
0xc166a323…1f33
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity